[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165114222645.2893052.12842449930657953509.b4-ty@kernel.org>
Date: Thu, 28 Apr 2022 14:50:27 +0100
From: Will Deacon <will@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>
Cc: kernel-team@...roid.com, Will Deacon <will@...nel.org>,
Jonathan Corbet <corbet@....net>,
Kees Cook <keescook@...omium.org>,
Luis Machado <luis.machado@....com>,
linux-kernel@...r.kernel.org,
Richard Earnshaw <Richard.Earnshaw@....com>,
Eric Biederman <ebiederm@...ssion.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] elf: Fix the arm64 MTE ELF segment name and value
On Mon, 25 Apr 2022 16:18:33 +0100, Catalin Marinas wrote:
> Unfortunately, the name/value choice for the MTE ELF segment type
> (PT_ARM_MEMTAG_MTE) was pretty poor: LOPROC+1 is already in use by
> PT_AARCH64_UNWIND, as defined in the AArch64 ELF ABI
> (https://github.com/ARM-software/abi-aa/blob/main/aaelf64/aaelf64.rst).
>
> Update the ELF segment type value to LOPROC+2 and also change the define
> to PT_AARCH64_MEMTAG_MTE to match the AArch64 ELF ABI namespace. The
> AArch64 ELF ABI document is updating accordingly (segment type not
> previously mentioned in the document).
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] elf: Fix the arm64 MTE ELF segment name and value
https://git.kernel.org/arm64/c/c35fe2a68f29
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists