linux-kernel - Re: [PATCH 0/5] kbuild: uapi: improvements to header testing

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] [day] [month] [year] [list]

Message-ID: <20251230203156.GD4062669@ax162>
Date: Tue, 30 Dec 2025 13:31:56 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Nicolas Schier <nsc@...nel.org>, Brian Cain <bcain@...nel.org>,
	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
	bpf@...r.kernel.org, linux-hexagon@...r.kernel.org
Subject: Re: [PATCH 0/5] kbuild: uapi: improvements to header testing

Hi Thomas,

On Tue, Dec 23, 2025 at 08:04:07AM +0100, Thomas Weißschuh wrote:
> Also validate that UAPI headers do not depend on libc and remove the
> dependency on CC_CAN_LINK.
> 
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
> ---
> Thomas Weißschuh (5):
>       kbuild: uapi: validate that headers do not use libc
>       hexagon: Drop invalid UAPI header asm/signal.h
>       kbuild: uapi: don't compile test bpf_perf_event.h on xtensa
>       kbuild: uapi: split out command conditions into variables
>       kbuild: uapi: drop dependency on CC_CAN_LINK
> 
>  arch/hexagon/include/{uapi => }/asm/signal.h |  0
>  init/Kconfig                                 |  2 +-
>  usr/include/Makefile                         | 87 +++++++++++++++++++++++++++-
>  3 files changed, 87 insertions(+), 2 deletions(-)

This seems like a great improvement to the UAPI header testing. I don't
see any immediate problems and it works for me in my brief local
testing. I will give a week or so for comments before I apply this to
kbuild-next (plus -next should be operating at that point).

Cheers,
Nathan