From: Mark Brown <broonie@kernel.org>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Dave Martin <dave.martin@arm.com>,
"H . J . Lu" <hjl.tools@gmail.com>,
Yu-cheng Yu <yu-cheng.yu@intel.com>,
linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
libc-alpha@sourceware.org
Subject: Re: [PATCH v2 0/3] arm64: Enable BTI for the executable as well as the interpreter
Date: Mon, 14 Jun 2021 17:00:22 +0100 [thread overview]
Message-ID: <20210614160022.GD5646@sirena.org.uk> (raw)
In-Reply-To: <43e67d7b-aab9-db1f-f74b-a87ba7442d47@arm.com>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
On Thu, Jun 10, 2021 at 11:28:12AM -0500, Jeremy Linton wrote:
> Of course, there is a good chance I've messed something up or i'm missing
> something. I should really validate the /lib/ld-linux behavior itself too. I
> guess this could just as well be a glibc issue (f34 has glibc 2.33-5 which
If it were a glibc issue that'd mean that glibc would have to somehow
manage to disable PROT_BTI after the kernel set it. I think I've found
the issue, will send a new version out shortly - we just weren't
actually parsing the properties on the main executable properly. A new
version should appear shortly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-06-14 16:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 11:24 [PATCH v2 0/3] arm64: Enable BTI for the executable as well as the interpreter Mark Brown
2021-06-04 11:24 ` [PATCH v2 1/3] elf: Allow architectures to parse properties on the main executable Mark Brown
2021-06-09 15:16 ` Dave Martin
2021-06-10 13:41 ` Mark Brown
2021-06-04 11:24 ` [PATCH v2 2/3] arm64: Enable BTI for main executable as well as the interpreter Mark Brown
2021-06-09 15:17 ` Dave Martin
2021-06-10 13:19 ` Mark Brown
2021-06-10 15:34 ` Dave Martin
2021-06-04 11:24 ` [PATCH v2 3/3] elf: Remove has_interp property from arch_adjust_elf_prot() Mark Brown
2021-06-09 15:17 ` Dave Martin
2021-06-09 16:55 ` Yu, Yu-cheng
2021-06-10 9:58 ` Dave Martin
2021-06-10 18:17 ` Yu, Yu-cheng
2021-06-10 13:34 ` Mark Brown
2021-06-10 15:40 ` Dave Martin
2021-06-10 16:28 ` [PATCH v2 0/3] arm64: Enable BTI for the executable as well as the interpreter Jeremy Linton
2021-06-14 16:00 ` Mark Brown [this message]
2021-06-15 15:22 ` Dave Martin
2021-06-15 15:33 ` Mark Brown
2021-06-15 15:41 ` Dave Martin
2021-06-16 5:12 ` Jeremy Linton
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=20210614160022.GD5646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dave.martin@arm.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 NNTP newsgroup(s).