public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/arm/morello/main] aarch64: morello: define PROT_MAX
Date: Wed, 26 Oct 2022 15:14:56 +0000 (GMT)	[thread overview]
Message-ID: <20221026151456.6E7BB384A078@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c47a360d0167266a2de87eac956f04c1d5ddac5f

commit c47a360d0167266a2de87eac956f04c1d5ddac5f
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date:   Fri Oct 21 12:10:11 2022 +0100

    aarch64: morello: define PROT_MAX
    
    Specifies the prot flags a mapping may gain via mprotect or MAP_FIXED.
    On CHERI targets this is used to get capability with more permissions
    than the original mmap protection would imply.

Diff:
---
 sysdeps/unix/sysv/linux/aarch64/bits/mman.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/sysdeps/unix/sysv/linux/aarch64/bits/mman.h b/sysdeps/unix/sysv/linux/aarch64/bits/mman.h
index d7ac2fa993..8dbd8d6819 100644
--- a/sysdeps/unix/sysv/linux/aarch64/bits/mman.h
+++ b/sysdeps/unix/sysv/linux/aarch64/bits/mman.h
@@ -25,6 +25,9 @@
 
 #define PROT_BTI	0x10
 #define PROT_MTE	0x20
+#ifdef __CHERI_PURE_CAPABILITY__
+# define PROT_MAX(prot) ((prot) << 16)
+#endif
 
 #include <bits/mman-map-flags-generic.h>

             reply	other threads:[~2022-10-26 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 15:14 Szabolcs Nagy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-23 14:43 Szabolcs Nagy
2022-10-27 13:53 Szabolcs Nagy
2022-10-26 14:49 Szabolcs Nagy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221026151456.6E7BB384A078@sourceware.org \
    --to=nsz@sourceware.org \
    --cc=glibc-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).