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] cheri: elf: elfptr_t l_map_start in link_map struct
Date: Wed, 26 Oct 2022 15:16:33 +0000 (GMT)	[thread overview]
Message-ID: <20221026151633.8F89D3846446@sourceware.org> (raw)

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

commit 6b86cb6bf1a61f52c03f466742ebebcc746853aa
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date:   Thu Apr 7 13:18:48 2022 +0100

    cheri: elf: elfptr_t l_map_start in link_map struct
    
    Use a capability for the load segment start that covers all load
    segments so pointers can be derived from it.
    
    It should have RX permission and a separate capability used for
    writable pointers.

Diff:
---
 include/link.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/include/link.h b/include/link.h
index 0ac82d7c77..7632ae33d3 100644
--- a/include/link.h
+++ b/include/link.h
@@ -252,7 +252,8 @@ struct link_map
 
     /* Start and finish of memory map for this object.  l_map_start
        need not be the same as l_addr.  */
-    ElfW(Addr) l_map_start, l_map_end;
+    elfptr_t l_map_start;
+    ElfW(Addr) l_map_end;
     /* End of the executable part of the mapping.  */
     ElfW(Addr) l_text_end;

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 15:16 Szabolcs Nagy [this message]
2022-10-27 13:55 Szabolcs Nagy
2022-11-23 14:45 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=20221026151633.8F89D3846446@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).