From: Dave Martin <Dave.Martin@arm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jann Horn <jannh@google.com>, "H.J. Lu" <hjl.tools@gmail.com>,
Eugene Syromiatnikov <esyr@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
Yu-cheng Yu <yu-cheng.yu@intel.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: [RFC PATCH v2 0/2] ELF: Alternate program property parser
Date: Fri, 23 Aug 2019 18:23:38 +0100 [thread overview]
Message-ID: <1566581020-9953-1-git-send-email-Dave.Martin@arm.com> (raw)
This series is an experimental reimplementation of ELF property parsing
(see NT_GNU_PROPERTY_TYPE_0, [1]) for the ELF loader.
This is intended for comparison / merging with [2] (or could replace it,
if people think this approach is better).
This supersedes RFC v1 [3].
For changes see the individual patches.
[1] Linux Extensions to gABI
https://github.com/hjl-tools/linux-abi/wiki/Linux-Extensions-to-gABI
[2] [PATCH v8 22/27] binfmt_elf: Extract .note.gnu.property from an ELF file
https://lore.kernel.org/lkml/20190813205225.12032-23-yu-cheng.yu@intel.com/
[3] [RFC PATCH 0/2] ELF: Alternate program property parser
https://lore.kernel.org/lkml/1566295063-7387-1-git-send-email-Dave.Martin@arm.com/
Dave Martin (2):
ELF: UAPI and Kconfig additions for ELF program properties
ELF: Add ELF program property parsing support
fs/Kconfig.binfmt | 3 ++
fs/binfmt_elf.c | 124 +++++++++++++++++++++++++++++++++++++++++++++++
fs/compat_binfmt_elf.c | 4 ++
include/linux/elf.h | 27 +++++++++++
include/uapi/linux/elf.h | 5 ++
5 files changed, 163 insertions(+)
--
2.1.4
next reply other threads:[~2019-08-23 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 17:23 Dave Martin [this message]
2019-08-23 17:23 ` [RFC PATCH v2 1/2] ELF: UAPI and Kconfig additions for ELF program properties Dave Martin
2019-08-23 17:23 ` [RFC PATCH v2 2/2] ELF: Add ELF program property parsing support Dave Martin
2019-08-30 5:37 ` Kees Cook
2019-08-30 8:34 ` Dave Martin
2019-08-30 17:03 ` Yu-cheng Yu
2019-09-02 9:28 ` Dave Martin
2019-09-03 22:29 ` Yu-cheng Yu
2019-09-04 11:05 ` Dave Martin
2019-09-04 16:50 ` Kees Cook
2019-09-05 7:57 ` Dave Martin
2019-10-09 12:59 ` Dave Martin
2019-10-10 21:00 ` Kees Cook
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=1566581020-9953-1-git-send-email-Dave.Martin@arm.com \
--to=dave.martin@arm.com \
--cc=esyr@redhat.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=yu-cheng.yu@intel.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 NNTP newsgroup(s).