From: Kees Cook <keescook@chromium.org>
To: will@kernel.org, broonie@kernel.org, catalin.marinas@arm.com
Cc: linux-arm-kernel@lists.infradead.org, jeremy.linton@arm.com,
hjl.tools@gmail.com, libc-alpha@sourceware.org,
szabolcs.nagy@arm.com, yu-cheng.yu@intel.com,
ebiederm@xmission.com, linux-arch@vger.kernel.org
Subject: Re: [PATCH v13 0/2] arm64: Enable BTI for the executable as well as the interpreter
Date: Wed, 20 Apr 2022 09:51:39 -0700 [thread overview]
Message-ID: <202204200951.68BC793FC3@keescook> (raw)
In-Reply-To: <165043278356.1481705.13924459838445776007.b4-ty@chromium.org>
On Tue, Apr 19, 2022 at 10:33:06PM -0700, Kees Cook wrote:
> On Tue, 19 Apr 2022 11:51:54 +0100, Mark Brown wrote:
> > Deployments of BTI on arm64 have run into issues interacting with
> > systemd's MemoryDenyWriteExecute feature. Currently for dynamically
> > linked executables the kernel will only handle architecture specific
> > properties like BTI for the interpreter, the expectation is that the
> > interpreter will then handle any properties on the main executable.
> > For BTI this means remapping the executable segments PROT_EXEC |
> > PROT_BTI.
> >
> > [...]
>
> Applied to for-next/execve, thanks!
Now un-applied! :)
--
Kees Cook
prev parent reply other threads:[~2022-04-20 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 10:51 Mark Brown
2022-04-19 10:51 ` [PATCH v13 1/2] elf: Allow architectures to parse properties on the main executable Mark Brown
2022-04-20 16:51 ` Kees Cook
2022-04-19 10:51 ` [PATCH v13 2/2] arm64: Enable BTI for main executable as well as the interpreter Mark Brown
2022-04-20 5:33 ` [PATCH v13 0/2] arm64: Enable BTI for the " Kees Cook
2022-04-20 9:36 ` Will Deacon
2022-04-20 9:57 ` Catalin Marinas
2022-04-20 11:57 ` Mark Brown
2022-04-20 13:39 ` Jeremy Linton
2022-04-20 16:51 ` Kees Cook
2022-04-21 9:34 ` Catalin Marinas
2022-04-21 15:52 ` Jeremy Linton
2022-04-21 17:58 ` Mark Brown
2022-04-20 16:48 ` Kees Cook
2022-04-20 16:51 ` Kees Cook [this message]
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=202204200951.68BC793FC3@keescook \
--to=keescook@chromium.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=ebiederm@xmission.com \
--cc=hjl.tools@gmail.com \
--cc=jeremy.linton@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=szabolcs.nagy@arm.com \
--cc=will@kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).