From: Yu-cheng Yu <yu-cheng.yu@intel.com>
To: Dave Martin <Dave.Martin@arm.com>
Cc: x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-mm@kvack.org, linux-arch@vger.kernel.org,
linux-api@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Andy Lutomirski <luto@amacapital.net>,
Balbir Singh <bsingharora@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Eugene Syromiatnikov <esyr@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
"H.J. Lu" <hjl.tools@gmail.com>, Jann Horn <jannh@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Kees Cook <keescook@chromium.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Nadav Amit <nadav.amit@gmail.com>,
Oleg Nesterov <oleg@redhat.com>, Pavel Machek <pavel@ucw.cz>,
Peter Zijlstra <peterz@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
Vedvyas Shanbhogue <vedvyas.shanbhogue@intel.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCH] binfmt_elf: Extract .note.gnu.property from an ELF file
Date: Thu, 02 May 2019 08:47:06 -0700 [thread overview]
Message-ID: <5b2c6cee345e00182e97842ae90c02cdcd830135.camel@intel.com> (raw)
In-Reply-To: <20190502111003.GO3567@e103592.cambridge.arm.com>
On Thu, 2019-05-02 at 12:10 +0100, Dave Martin wrote:
> On Wed, May 01, 2019 at 02:12:17PM -0700, Yu-cheng Yu wrote:
> > An ELF file's .note.gnu.property indicates features the executable file
> > can support. For example, the property GNU_PROPERTY_X86_FEATURE_1_AND
> > indicates the file supports GNU_PROPERTY_X86_FEATURE_1_IBT and/or
> > GNU_PROPERTY_X86_FEATURE_1_SHSTK.
[...]
> A couple of questions before I look in more detail:
>
> 1) Can we rely on PT_GNU_PROPERTY being present in the phdrs to describe
> the NT_GNU_PROPERTY_TYPE_0 note? If so, we can avoid trying to parse
> irrelevant PT_NOTE segments.
Some older linkers can create multiples of NT_GNU_PROPERTY_TYPE_0. The code
scans all PT_NOTE segments to ensure there is only one NT_GNU_PROPERTY_TYPE_0.
If there are multiples, then all are considered invalid.
>
>
> 2) Are there standard types for things like the program property header?
> If not, can we add something in elf.h? We should try to coordinate with
> libc on that. Something like
>
> typedef __u32 Elf_Word;
>
> typedef struct {
> Elf_Word pr_type;
> Elf_Word pr_datasz;
> } Elf_Gnu_Prophdr;
>
> (i.e., just the header part from [1], with a more specific name -- which
> I just made up).
Yes, I will fix that.
[...]
> 3) It looks like we have to go and re-parse all the notes for every
> property requested by the arch code.
As explained above, it is necessary to scan all PT_NOTE segments. But there
should be only one NT_GNU_PROPERTY_TYPE_0 in an ELF file. Once that is found,
perhaps we can store it somewhere, or call into the arch code as you mentioned
below. I will look into that.
>
> For now there is only one property requested anyway, so this is probably
> not too bad. But could we flip things around so that we have some
> CONFIG_ARCH_WANTS_ELF_GNU_PROPERTY (say), and have the ELF core code
> call into the arch backend for each property found?
>
> The arch could provide some hook
>
> int arch_elf_has_gnu_property(const Elf_Gnu_Prophdr *prop,
> const void *data);
>
> to consume the properties as they are found.
>
> This would effectively replace the arch_setup_property() hook you
> currently have.
>
> Cheers
> ---Dave
>
> [1] https://github.com/hjl-tools/linux-abi/wiki/Linux-Extensions-to-gABI
next prev parent reply other threads:[~2019-05-02 15:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 21:12 [PATCH] binfmt_elf: Extract .note.gnu.property from an ELF file Yu-cheng Yu
2019-05-01 21:37 ` Matthew Wilcox
2019-05-01 21:54 ` Yu-cheng Yu
2019-05-02 11:10 ` Dave Martin
2019-05-02 14:29 ` Dave Martin
2019-05-02 15:48 ` Yu-cheng Yu
2019-05-02 15:47 ` Yu-cheng Yu [this message]
2019-05-02 16:14 ` Dave Martin
2019-05-02 16:25 ` Yu-cheng Yu
2019-06-26 17:14 ` Andy Lutomirski
2019-06-26 17:30 ` Yu-cheng Yu
2019-06-27 9:27 ` Dave Martin
2019-06-27 9:38 ` Florian Weimer
2019-06-29 23:51 ` Andy Lutomirski
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=5b2c6cee345e00182e97842ae90c02cdcd830135.camel@intel.com \
--to=yu-cheng.yu@intel.com \
--cc=Dave.Martin@arm.com \
--cc=arnd@arndb.de \
--cc=bsingharora@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=esyr@redhat.com \
--cc=fweimer@redhat.com \
--cc=gorcunov@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mike.kravetz@oracle.com \
--cc=mingo@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=oleg@redhat.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=rdunlap@infradead.org \
--cc=szabolcs.nagy@arm.com \
--cc=tglx@linutronix.de \
--cc=vedvyas.shanbhogue@intel.com \
--cc=x86@kernel.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 NNTP newsgroup(s).