From: Kees Cook <keescook@chromium.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Hector Marco-Gisbert <hecmargi@upv.es>,
Jason Gunthorpe <jgg@mellanox.com>
Subject: [GIT PULL] READ_IMPLIES_EXEC cleanup for -tip next
Date: Mon, 2 Mar 2020 20:25:56 -0800 [thread overview]
Message-ID: <202003022019.7A20027@keescook> (raw)
Hi Thomas,
Please pull these READ_IMPLIES_EXEC cleanups. They've got Acks, and have
been sitting without further commented since v4:
https://lore.kernel.org/lkml/20200225051307.6401-1-keescook@chromium.org/#r
Catalin specifically asked me during Plumbers if I could get this series
refreshed and finalized, so here we are! :) I'd wanted to keep these all
together so per-arch RIE special cases were changed at the same time.
Thanks!
-Kees
The following changes since commit 11a48a5a18c63fd7621bb050228cebf13566e4d8:
Linux 5.6-rc2 (2020-02-16 13:16:59 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/rie-cleanup-next
for you to fetch changes up to 631551ed971466e4a7ea0b6b11a4ddf2b80513d3:
arm64, elf: Disable automatic READ_IMPLIES_EXEC for 64-bit address spaces (2020-02-24 21:00:51 -0800)
----------------------------------------------------------------
READ_IMPLIES_EXEC cleanups
- Fix READ_IMPLIES_EXEC across x86, arm64, and arm
----------------------------------------------------------------
Kees Cook (6):
x86/elf: Add table to document READ_IMPLIES_EXEC
x86/elf: Split READ_IMPLIES_EXEC from executable GNU_STACK
x86/elf: Disable automatic READ_IMPLIES_EXEC for 64-bit address spaces
arm32/64, elf: Add tables to document READ_IMPLIES_EXEC
arm32/64, elf: Split READ_IMPLIES_EXEC from executable GNU_STACK
arm64, elf: Disable automatic READ_IMPLIES_EXEC for 64-bit address spaces
arch/arm/kernel/elf.c | 27 +++++++++++++++++++++++----
arch/arm64/include/asm/elf.h | 23 ++++++++++++++++++++++-
arch/x86/include/asm/elf.h | 22 +++++++++++++++++++++-
fs/compat_binfmt_elf.c | 5 +++++
4 files changed, 71 insertions(+), 6 deletions(-)
--
Kees Cook
reply other threads:[~2020-03-03 4:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202003022019.7A20027@keescook \
--to=keescook@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=hecmargi@upv.es \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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