public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30452] LD_PREFER_MAP_32BIT_EXEC does not work with 2MiB load segment alignment
Date: Fri, 30 Jun 2023 17:43:15 +0000	[thread overview]
Message-ID: <bug-30452-131-4YUYouhHjV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30452-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30452

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=6259ab39410cdefc80077afea48ca9cb057f6005

commit 6259ab39410cdefc80077afea48ca9cb057f6005
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Thu Jun 22 14:30:31 2023 -0700

    ld.so: Always use MAP_COPY to map the first segment [BZ #30452]

    The first segment in a shared library may be read-only, not executable.
    To support LD_PREFER_MAP_32BIT_EXEC on such shared libraries, we also
    check MAP_DENYWRITE to decide if MAP_32BIT should be passed to mmap.
    Normally the first segment is mapped with MAP_COPY, which is defined
    as (MAP_PRIVATE | MAP_DENYWRITE).  But if the segment alignment is
    greater than the page size, MAP_COPY isn't used to allocate enough
    space to ensure that the segment can be properly aligned.  Map the
    first segment with MAP_COPY in this case to fix BZ #30452.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-06-30 17:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 14:13 [Bug dynamic-link/30452] New: elf/tst-map-32bit-1a fails with binutils-2.30-117.el8.x86_64 fweimer at redhat dot com
2023-05-16 14:16 ` [Bug dynamic-link/30452] LD_PREFER_MAP_32BIT_EXEC does not work with 2MiB load segment alignment fweimer at redhat dot com
2023-05-17 18:38 ` hjl.tools at gmail dot com
2023-05-17 18:45 ` fweimer at redhat dot com
2023-05-17 20:16 ` hjl.tools at gmail dot com
2023-05-18 17:22 ` hjl.tools at gmail dot com
2023-06-30 17:43 ` cvs-commit at gcc dot gnu.org [this message]

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=bug-30452-131-4YUYouhHjV@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).