public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86-64: Restore LD_PREFER_MAP_32BIT_EXEC support [BZ #28656]
Date: Tue, 02 Aug 2022 10:00:43 +0200	[thread overview]
Message-ID: <87o7x3847o.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20220801195150.2160919-1-hjl.tools@gmail.com> (H. J. Lu via Libc-alpha's message of "Mon, 1 Aug 2022 12:51:50 -0700")

* H. J. Lu via Libc-alpha:

> Crossing 2GB boundaries with indirect calls and jumps can use more
> branch prediction resources on several Intel CPUs.  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 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.

If the performance benefits are significant, this should be handled at
the kernel level.  Only the kernel can put the main program, ld.so and
the vDSO into the same 2GB window (presumably with the main program at
the top, so that the heap can grow almost indefinitely).

For mapping shared objects, we can give the kernel a hint that they will
eventually contain an executable mapping.  If the kernel could reuse
MAP_DENYWRITE for that, no glibc changes would be needed after all.

Doing this is in glibc is only a very partial solution, and so I'd
appreciate if it could be fixed properly in the kernel.

Thanks,
Florian


  reply	other threads:[~2022-08-02  8:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 19:51 H.J. Lu
2022-08-02  8:00 ` Florian Weimer [this message]
2022-08-05 21:53   ` H.J. Lu
2022-08-08 13:29     ` Florian Weimer
2022-08-08 17:02       ` H.J. Lu
2023-01-26 17:22 H.J. Lu
2023-02-09 14:35 ` Florian Weimer
2023-02-10 16:50   ` H.J. Lu
2023-02-10 21:54     ` Carlos O'Donell
2023-02-10 22:22       ` 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=87o7x3847o.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.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).