From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Fangrui Song <maskray@google.com>,
"Zhang, Annita" <annita.zhang@intel.com>,
gnu-gabi <gnu-gabi@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: binutils ld and new PT_GNU_PROPERTY segment
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <CAMe9rOqXY+hrQqxLwj0fCK_trRqdiCE54iUqZ5PovS7uQ027XA@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOpgwi0M9XqbeyUm+LLuqypObZBmEGEAgFAyDeUYck5ucA@mail.gmail.com>
On Wed, Feb 19, 2020 at 4:28 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Wed, Feb 19, 2020 at 4:02 AM Mark Wielaard <mark@klomp.org> wrote:
> >
> > Hi,
> >
> > On Wed, 2020-02-19 at 03:39 -0800, H.J. Lu wrote:
> > > On Wed, Feb 19, 2020 at 2:58 AM Mark Wielaard <mark@klomp.org> wrote:
> > > > On Tue, 2020-02-18 at 18:31 -0800, Fangrui Song wrote:
> > > > > From what I can see, neither the Linux kernel nor glibc uses
> > > > > PT_GNU_PROPERTY.
> > > > > glibc/sysdeps/x86/dl-prop.h parses PT_NOTE.
> > > >
> > > > That is my impression too.
> > >
> > > See:
> > >
> > > https://patchwork.kernel.org/patch/11285409/
> > >
> > > It is for both x86 and arm64.
> >
> > So that is not upstream in the mainline kernel? Why can't that patch
> > use the existing PT_NOTE segment? That would make it compatible with
> > existing binaries that don't have this PT_GNU_PROPERTY program header.
>
> Kernel loader is one of motivations of PT_GNU_PROPERTY. Kernel loader
> only wants to check PT_XXX.
>
This is one thread on kernel mailing list:
https://lore.kernel.org/lkml/87imt4jwpt.fsf@oldenburg2.str.redhat.com/
--
H.J.
next prev parent reply other threads:[~2020-02-19 12:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 0:00 Mark Wielaard
2020-01-01 0:00 ` H.J. Lu
2020-01-01 0:00 ` Fangrui Song via gnu-gabi
2020-01-01 0:00 ` Zhang, Annita
2020-01-01 0:00 ` Mark Wielaard
2020-01-01 0:00 ` H.J. Lu
2020-01-01 0:00 ` Mark Wielaard
2020-01-01 0:00 ` H.J. Lu
2020-01-01 0:00 ` H.J. Lu [this message]
2020-01-01 0:00 ` Mark Wielaard
2020-01-01 0:00 ` H.J. Lu
2020-01-01 0:00 ` Fangrui Song
2020-01-01 0:00 ` H.J. Lu
2020-01-01 0:00 ` Mark Wielaard
2020-01-01 0:00 ` H.J. Lu
2020-01-01 0:00 ` Mark Wielaard
2020-01-01 0:00 ` H.J. Lu
2020-01-01 0:00 ` Mark Wielaard
2020-01-01 0:00 ` Fangrui Song
2020-04-01 8:46 ` Florian Weimer
2020-04-01 9:22 ` Szabolcs Nagy
2020-04-01 9:29 ` Florian Weimer
2020-04-01 10:10 ` Szabolcs Nagy
2020-04-01 10:21 ` Florian Weimer
2020-01-01 0:00 ` Fangrui Song
2020-01-01 0:00 ` H.J. Lu
2020-01-01 0:00 ` Mark Wielaard
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=CAMe9rOqXY+hrQqxLwj0fCK_trRqdiCE54iUqZ5PovS7uQ027XA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=annita.zhang@intel.com \
--cc=binutils@sourceware.org \
--cc=gnu-gabi@sourceware.org \
--cc=mark@klomp.org \
--cc=maskray@google.com \
/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).