From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH v3] elf: Set p_align to the minimum page size if possible
Date: Fri, 14 Jan 2022 05:03:52 -0800 [thread overview]
Message-ID: <CAMe9rOruNa9Z2saFq0h14uV+Hz2Ds7z+jXnN2eqBmiVeMR5h8Q@mail.gmail.com> (raw)
In-Reply-To: <11e134a2-1ee7-bec4-fa03-1d76609923f7@suse.com>
On Fri, Jan 14, 2022 at 12:27 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 29.12.2021 20:39, H.J. Lu via Binutils wrote:
> > --- a/ld/testsuite/ld-elf/linux-x86.exp
> > +++ b/ld/testsuite/ld-elf/linux-x86.exp
> > @@ -185,6 +185,42 @@ run_ld_link_exec_tests [list \
> > "" \
> > "tmpdir/indirect-extern-access-2.so" \
> > ] \
> > + [list \
> > + "Run p_align-1a without PIE" \
> > + "$NOPIE_LDFLAGS" \
> > + "" \
> > + { p_align-1.c } \
> > + "p_align-1a" \
> > + "pass.out" \
> > + "$NOPIE_CFLAGS" \
> > + ] \
> > + [list \
> > + "Run p_align-1b with PIE" \
> > + "-pie" \
> > + "" \
> > + { p_align-1.c } \
> > + "p_align-1b" \
> > + "pass.out" \
> > + "-fpie" \
> > + ] \
> > + [list \
> > + "Run p_align-1c with -Wl,-z,max-page-size=0x1000 without PIE" \
> > + "$NOPIE_LDFLAGS -Wl,-z,max-page-size=0x1000" \
> > + "" \
> > + { p_align-1.c } \
> > + "p_align-1c" \
> > + "pass.out" \
> > + "$NOPIE_CFLAGS" \
> > + ] \
> > + [list \
> > + "Run p_align-1d with -Wl,-z,max-page-size=0x1000 with PIE" \
> > + "-pie -Wl,-z,max-page-size=0x1000" \
> > + "" \
> > + { p_align-1.c } \
> > + "p_align-1d" \
> > + "pass.out" \
> > + "-fpie" \
> > + ] \
> > ]
>
> The two PIE variants of this also fail for me on glibc 2.26. Looks
> like LOAD segments' alignment isn't being honored there, at least
> not if it's as big as it is here.
>
The PIE alignment needs the kernel fix:
commit ce81bb256a224259ab686742a6284930cbe4f1fa
Author: Chris Kennelly <ckennelly@google.com>
Date: Thu Oct 15 20:12:32 2020 -0700
fs/binfmt_elf: use PT_LOAD p_align values for suitable start address
--
H.J.
next prev parent reply other threads:[~2022-01-14 13:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 19:39 H.J. Lu
2022-01-14 8:12 ` Jan Beulich
2022-02-10 12:44 ` Jan Beulich
2022-01-14 8:27 ` Jan Beulich
2022-01-14 13:03 ` H.J. Lu [this message]
2022-01-14 13:40 ` Jan Beulich
2022-01-14 14:02 ` H.J. Lu
2022-01-14 14:07 ` Jan Beulich
2022-01-14 14:14 ` H.J. Lu
2022-01-17 10:38 ` Jan Beulich
2022-01-17 13:44 ` [PATCH] ld: Require GCC 8.0 for p_align-1.c tests H.J. Lu
2022-01-17 13:51 ` Jan Beulich
2022-01-17 13:54 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2021-12-25 3:54 [PATCH v3] elf: Set p_align to the minimum page size if possible H.J. Lu
2021-12-29 0:42 ` Alan Modra
2021-12-29 19:41 ` H.J. Lu
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=CAMe9rOruNa9Z2saFq0h14uV+Hz2Ds7z+jXnN2eqBmiVeMR5h8Q@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
/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).