linux-kernel - Re: [tip: x86/core] x86/cpufeatures: Generate the <asm/cpufeaturemasks.h> header based on build config

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: <20250328175606.5c7cc096@kernel.org>
Date: Fri, 28 Mar 2025 17:56:06 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>, "H. Peter Anvin (Intel)"
 <hpa@...or.com>, Michael Kelley <mhklinux@...look.com>, "Xin Li (Intel)"
 <xin@...or.com>, "Borislav Petkov (AMD)" <bp@...en8.de>, Ingo Molnar
 <mingo@...nel.org>, Nikolay Borisov <nik.borisov@...e.com>,
 "x86@...nel.org" <x86@...nel.org>, "linux-kernel@...r.kernel.org"
 <linux-kernel@...r.kernel.org>
Subject: Re: [tip: x86/core] x86/cpufeatures: Generate the
 <asm/cpufeaturemasks.h> header based on build config

On Fri, 28 Mar 2025 17:22:03 -0700 Linus Torvalds wrote:
> > So I think the real fix is something like this ENTIRELY UNTESTED
> > patch.  Whitespace-damaged again to make sure people don't apply this
> > mindlessly, it needs more thought:  
> 
> .. and that ended up being even more whitespace-damaged than I meant
> to make it, because it also line-wrapped.
> 
> Oh well. Not pretty, but I hope people still get the idea.
> 
> And I just actually tried doing a build after touching the .config
> file, and it did seem to work.

Excellent, can confirm that it works for me, too!

Thanks!!

> But since I had _also_ messed with the config file on purpose earlier,
> I'm not sure I'm actually testing the thing the networking builds
> trigger. So I might be entirely missing something.

FWIW the exact commands our build script uses are:

make W=1 LLVM=1 O=build_allmodconfig_cl -j 6 allmodconfig
./scripts/config --file build_allmodconfig_cl/.config -d werror -d kvm_werror -d drm_werror
make W=1 LLVM=1 O=build_allmodconfig_cl -j 6