From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: [PATCH 0/4] PR28824, relro security issues
Date: Tue, 8 Feb 2022 11:38:29 +1030 [thread overview]
Message-ID: <20220208010833.2103874-1-amodra@gmail.com> (raw)
The first two patches in this series fix relro protection for all
targets that might be running with MAXPAGESIZE larger than
COMMONPAGESIZE memory pages. They also fix pr28734, the extra page
gap between text and data segments when relro.
See the first patch for lots of detail on what is going on. I'll
leave this series a few days before committing in case someone spots a
bug or has constructive comments.
Alan Modra (4):
PR28824, relro security issues
PR28824, relro security issues, x86 keep COMMONPAGESIZE relro
Remove bfd ELF_RELROPAGESIZE
Don't pass around expld.dataseg pointer
bfd/bfd-in2.h | 2 +-
bfd/bfd.c | 9 +++----
bfd/elf-bfd.h | 3 ---
bfd/elf32-ppc.c | 1 -
bfd/elf64-ppc.c | 1 -
bfd/elfxx-target.h | 11 --------
ld/emultempl/elf-x86.em | 1 +
ld/ld.h | 4 +++
ld/ldemul.c | 3 +--
ld/ldexp.c | 33 ++++++++++++++++--------
ld/ldexp.h | 5 +++-
ld/ldlang.c | 43 ++++++++++++++++----------------
ld/testsuite/ld-x86-64/pr18176.d | 1 +
13 files changed, 59 insertions(+), 58 deletions(-)
next reply other threads:[~2022-02-08 1:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 1:08 Alan Modra [this message]
2022-02-08 1:08 ` [PATCH 1/4] " Alan Modra
2022-02-08 1:08 ` [PATCH 2/4] PR28824, relro security issues, x86 keep COMMONPAGESIZE relro Alan Modra
2022-02-14 2:18 ` Alan Modra
2022-02-14 3:13 ` H.J. Lu
2022-02-08 1:08 ` [PATCH 3/4] Remove bfd ELF_RELROPAGESIZE Alan Modra
2022-02-08 1:08 ` [PATCH 4/4] Don't pass around expld.dataseg pointer Alan Modra
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=20220208010833.2103874-1-amodra@gmail.com \
--to=amodra@gmail.com \
--cc=binutils@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).