linux-kernel - Re: [PATCH 23/23] binfmt_elf: Warn on missing or suspicious regset note names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <D620FCC4-4A72-45CB-AF16-456E2B49B5C8@kernel.org>
Date: Sat, 05 Jul 2025 08:14:33 -0700
From: Kees Cook <kees@...nel.org>
To: Dave Martin <Dave.Martin@....com>, linux-kernel@...r.kernel.org
CC: Oleg Nesterov <oleg@...hat.com>, Akihiko Odaki <akihiko.odaki@...nix.com>
Subject: Re: [PATCH 23/23] binfmt_elf: Warn on missing or suspicious regset note names



On July 1, 2025 6:56:16 AM PDT, Dave Martin <Dave.Martin@....com> wrote:
>Un-migrated arches will trigger WARNs with this patch applied, and
>arches that don't specify codedump note names will always get
>"LINUX" -- since the whole point is to stop guessing the note name in
>the core code.
>
>On _unpatched_ arches (only) this is a potential ABI break for the
>NT_PRFPREG note (which, for historical reasons, is a "CORE" note even
>though it is OS-specific on most or all arches).

After all your arch patches, aren't all the archs using the correct values? Is the WARN for new or out-of-tree archs?

-Kees

-- 
Kees Cook