From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arch@vger.kernel.org, Yu-cheng Yu <yu-cheng.yu@intel.com>,
libc-alpha@sourceware.org, Jeremy Linton <jeremy.linton@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/4] arm64: Enable BTI for the executable as well as the interpreter
Date: Thu, 17 Feb 2022 08:17:02 +0000 [thread overview]
Message-ID: <20220217081702.GI2692478@arm.com> (raw)
In-Reply-To: <Yg0t2srflG80zQKF@sirena.org.uk>
The 02/16/2022 17:01, Mark Brown wrote:
> On Wed, Feb 16, 2022 at 04:49:54PM +0000, Szabolcs Nagy wrote:
>
> > if we ever wanted to map bti marked binaries without PROT_BTI
> > and introduced a knob to do that in ld.so, then this change
> > would be problematic (we cannot easily remove PROT_BTI from
> > the exe), but we don't have such plans.
>
> In general or only in the case where MWDE is enabled (in which case it's
> the same problem as exists today trying to enable BTI in the presence of
> MWDE)?
ah yes with mwde only.
next prev parent reply other threads:[~2022-02-17 8:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 15:07 Mark Brown
2022-01-24 15:07 ` [PATCH v8 1/4] elf: Allow architectures to parse properties on the main executable Mark Brown
2022-02-04 13:00 ` Catalin Marinas
2022-01-24 15:07 ` [PATCH v8 2/4] arm64: Enable BTI for main executable as well as the interpreter Mark Brown
2022-02-04 13:11 ` Catalin Marinas
2022-01-24 15:07 ` [PATCH v8 3/4] elf: Remove has_interp property from arch_adjust_elf_prot() Mark Brown
2022-02-04 14:53 ` Catalin Marinas
2022-01-24 15:07 ` [PATCH v8 4/4] elf: Remove has_interp property from arch_parse_elf_property() Mark Brown
2022-02-04 14:54 ` Catalin Marinas
2022-02-15 18:34 ` [PATCH v8 0/4] arm64: Enable BTI for the executable as well as the interpreter Will Deacon
2022-02-16 13:34 ` Catalin Marinas
2022-02-16 16:49 ` Szabolcs Nagy
2022-02-16 17:01 ` Mark Brown
2022-02-17 8:17 ` Szabolcs Nagy [this message]
2022-02-22 14:15 ` Mark Brown
2022-02-25 13:53 ` Will Deacon
2022-02-25 15:11 ` Mark Brown
2022-02-25 15:54 ` Will Deacon
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=20220217081702.GI2692478@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.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=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).