From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH] x86-64: Restore LD_PREFER_MAP_32BIT_EXEC support [BZ #28656]
Date: Thu, 09 Feb 2023 15:35:36 +0100 [thread overview]
Message-ID: <87k00qkitj.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20230126172256.829709-1-hjl.tools@gmail.com> (H. J. Lu via Libc-alpha's message of "Thu, 26 Jan 2023 09:22:56 -0800")
* H. J. Lu via Libc-alpha:
> Crossing 2GB boundaries with indirect calls and jumps can use more
> branch prediction resources on Intel Golden Cove CPU (see the
> "Misprediction for Branches >2GB" section in Intel 64 and IA-32
> Architectures Optimization Reference Manual.) There is visible
> performance improvement on workloads with many PLT calls when executable
> and shared libraries are mmapped below 2GB. Add the Prefer_MAP_32BIT_EXEC
> bit so that mmap will try to map executable or denywrite pages in shared
> libraries with MAP_32BIT first.
>
> NB: Prefer_MAP_32BIT_EXEC reduces bits available for address space
> layout randomization (ASLR), which is always disabled for SUID programs
> and can only be enabled by setting environment variable,
> LD_PREFER_MAP_32BIT_EXEC. LD_PREFER_MAP_32BIT_EXEC works only between
> shared libraries or between shared libraries and executables with
> addresses below 2GB. PIEs are usually mapped above 4GB by the kernel.
I still think we should fix this in the kernel, using MAP_DENYWRITE as a
hint for placement. This way, it's easier to turn it on unconditionally
for the whole system because the lower 4 GiB will not be polluted by
code mappings.
Thanks,
Florian
next prev parent reply other threads:[~2023-02-09 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 17:22 H.J. Lu
2023-02-09 14:35 ` Florian Weimer [this message]
2023-02-10 16:50 ` H.J. Lu
2023-02-10 21:54 ` Carlos O'Donell
2023-02-10 22:22 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2022-08-01 19:51 H.J. Lu
2022-08-02 8:00 ` Florian Weimer
2022-08-05 21:53 ` H.J. Lu
2022-08-08 13:29 ` Florian Weimer
2022-08-08 17:02 ` 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=87k00qkitj.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).