[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202204281009.57198AEC9@keescook>
Date: Thu, 28 Apr 2022 10:09:04 -0700
From: Kees Cook <keescook@...omium.org>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Will Deacon <will@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Jonathan Corbet <corbet@....net>,
Eric Biederman <ebiederm@...ssion.com>,
Luis Machado <luis.machado@....com>,
Richard Earnshaw <Richard.Earnshaw@....com>
Subject: Re: [PATCH] elf: Fix the arm64 MTE ELF segment name and value
On Mon, Apr 25, 2022 at 04:18:33PM +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).
>
> Signed-off-by: Catalin Marinas <catalin.marinas@....com>
Reviewed-by: Kees Cook <keescook@...omium.org>
--
Kees Cook
Powered by blists - more mailing lists