From: Carlos O'Donell <carlos@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH v2] x86-64: Add glibc.cpu.prefer_map_32bit_exec [BZ #28656]
Date: Tue, 21 Feb 2023 16:41:55 -0500 [thread overview]
Message-ID: <dc70c1f2-ac86-495b-d1f0-473f21408827@redhat.com> (raw)
In-Reply-To: <CAMe9rOqHEaP-0kqcE9=i9RSwvMa0=iBmoxoMw8XDBgN+iqxASQ@mail.gmail.com>
On 2/21/23 11:35, H.J. Lu wrote:
>>> +/* Check that LD_PREFER_MAP_32BIT_EXEC works in PDE and shared library.
>>
>> s/PDE/PIE/g ?
>
> This feature won't work for PIE since PIE is usually loaded at a
> random address above
> 4GB by kernel. On the other hand, PDE (no-PIE) is loaded at a fixed
> address below 2GB.
Thanks. That makes sense. Leave this as PDE then and we'll start using PDE
everywhere we might have written no-PIE :-)
--
Cheers,
Carlos.
next prev parent reply other threads:[~2023-02-21 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 22:21 H.J. Lu
2023-02-21 15:11 ` Carlos O'Donell
2023-02-21 16:35 ` H.J. Lu
2023-02-21 21:41 ` Carlos O'Donell [this message]
2023-02-21 21:53 ` 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=dc70c1f2-ac86-495b-d1f0-473f21408827@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@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).