linux-kernel - Re: [PATCH v3 0/3] kbuild: userprogs: introduce architecture-specific CC_CAN

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: <176355344004.27328.4435801280673856059.b4-ty@kernel.org>
Date: Wed, 19 Nov 2025 12:58:13 +0100
From: Nicolas Schier <nsc@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>,
	Nicolas Schier <nicolas.schier@...ux.dev>,
	Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Nicolas Schier <nsc@...nel.org>,
	linux-kernel@...r.kernel.org,
	linux-kbuild@...r.kernel.org
Subject: Re: [PATCH v3 0/3] kbuild: userprogs: introduce architecture-specific CC_CAN_LINK and userprog flags

On Fri, 14 Nov 2025 14:43:55 +0100, Thomas Weißschuh wrote:
> The current logic to inherit -m32/-m64 from the kernel build only works
> for a few architectures. It does not handle byte order differences,
> architectures using different compiler flags or different kinds of ABIs.
> 
> Introduce a per-architecture override mechanism to set CC_CAN_LINK and
> the flags used for userprogs.
> This revision only contains the generic kbuild infrastructure bits.
> The architecture-specific will go through the architecture trees.
> They are present in v2 of the series linked below.
> 
> [...]

Applied to kbuild-next, thanks!

[1/3] kbuild: don't enable CC_CAN_LINK if the dummy program generates warnings
      https://git.kernel.org/kbuild/c/d81d9d38
[2/3] init: deduplicate cc-can-link.sh invocations
      https://git.kernel.org/kbuild/c/80623f2c
[3/3] kbuild: allow architectures to override CC_CAN_LINK
      https://git.kernel.org/kbuild/c/deab487e

Please note that commit hashes might change in case of issues with
kbuild-next.

Best regards,
-- 
Nicolas