linux-kernel - Re: [PATCH 0/2] kbuild: enable 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: <CANiq72=rhY_k1RRJoTzsY8PnEW5D=m2Org9m0v3erJsWxW4HkQ@mail.gmail.com>
Date: Tue, 12 Aug 2025 12:50:44 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nicolas.schier@...ux.dev>, 
	Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, 
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>, 
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, 
	Danilo Krummrich <dakr@...nel.org>, linux-kbuild@...r.kernel.org, 
	linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH 0/2] kbuild: enable CONFIG_WERROR for more build steps

On Tue, Aug 12, 2025 at 12:25 PM Thomas Weißschuh
<thomas.weissschuh@...utronix.de> wrote:
>
> The users will still pass -Werror explicitly, we can't filter that out.

You mean the user passing them when calling `make`, right? I guess we
could perhaps try to be smart there, but yeah, it gets annoying.

Another option could be to have a new `NOCONFIGCC` that gets used only
for Kconfig and that defaults to `HOSTCC`.

> Let's skip hostprogs for now.

Sounds good, thanks!

> Another possibility would be to use -Werror
> for hostprogs unconditionally. Various tools/ are doing that for example.

Not sure what Kbuild thinks about that -- we have a small risk of
breaking things with newer compilers, but that may be not too bad for
just hostprogs (unlike when it was attempted to make it default `y`).

(For Rust, the rate of new releases is very high compared to GCC or
LLVM, but on the other hand it is easy to test them in advance, and
what I have done so far for other things is just clean them as they
appear -- so that should be fine, but it does make it way more urgent
if they are errors every time, though, since it blocks other testing
too).

Cheers,
Miguel