public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30452] New: elf/tst-map-32bit-1a fails with binutils-2.30-117.el8.x86_64
Date: Tue, 16 May 2023 14:13:51 +0000 [thread overview]
Message-ID: <bug-30452-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30452
Bug ID: 30452
Summary: elf/tst-map-32bit-1a fails with
binutils-2.30-117.el8.x86_64
Product: glibc
Version: 2.38
Status: NEW
Severity: normal
Priority: P2
Component: dynamic-link
Assignee: unassigned at sourceware dot org
Reporter: fweimer at redhat dot com
Target Milestone: ---
Target: x86_64-linux-gnu
For some reason, BFD ld produces load segments which are 2 MiB aligned:
LOAD 0x000000 0x0000000000000000 0x0000000000000000 0x000ff0
0x000ff0 R E 0x200000
LOAD 0x001e00 0x0000000000201e00 0x0000000000201e00 0x000270
0x000280 RW 0x200000
This means that the fast path in _dl_map_segment is not taken, and the
combination of address zero with MAP_DENYWRITE is never used, so MAP_32BIT
handling does not kick in.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-05-16 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 14:13 fweimer at redhat dot com [this message]
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
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@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).