[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175695795639.3712216.15743949549231818751.b4-ty@kernel.org>
Date: Wed, 3 Sep 2025 20:52:40 -0700
From: Kees Cook <kees@...nel.org>
To: linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org,
Svetlana Parfenova <svetlana.parfenova@...tacore.com>
Cc: Kees Cook <kees@...nel.org>,
paul.walmsley@...ive.com,
palmer@...belt.com,
aou@...s.berkeley.edu,
alex@...ti.f,
viro@...iv.linux.org.uk,
brauner@...nel.org,
jack@...e.cz,
akpm@...ux-foundation.org,
david@...hat.com,
lorenzo.stoakes@...cle.com,
Liam.Howlett@...cle.com,
vbabka@...e.cz,
rppt@...nel.org,
surenb@...gle.com,
mhocko@...e.com
Subject: Re: [RFC RESEND v3] binfmt_elf: preserve original ELF e_flags for core dumps
On Mon, 01 Sep 2025 20:53:50 +0700, Svetlana Parfenova wrote:
> Some architectures, such as RISC-V, use the ELF e_flags field to encode
> ABI-specific information (e.g., ISA extensions, fpu support). Debuggers
> like GDB rely on these flags in core dumps to correctly interpret
> optional register sets. If the flags are missing or incorrect, GDB may
> warn and ignore valid data, for example:
>
> warning: Unexpected size of section '.reg2/213' in core file.
>
> [...]
Applied to for-next/execve, thanks!
[1/1] binfmt_elf: preserve original ELF e_flags for core dumps
https://git.kernel.org/kees/c/8c94db0ae97c
Take care,
--
Kees Cook
Powered by blists - more mailing lists