linux-kernel - Re: linux-next: build warning after merge of Linus' tree

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: <20250422204847.GA670608@ax162>
Date: Tue, 22 Apr 2025 13:48:47 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Thomas Weißschuh <linux@...ssschuh.net>,
	Masahiro Yamada <masahiroy@...nel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of Linus' tree

On Tue, Apr 22, 2025 at 11:20:21AM -0700, Linus Torvalds wrote:
> Heh. We have several other cases of that "disable warning" pattern
> that does *not* use that cc-disable-warning thing.
> 
> In fact, right next to the new unterminated-string-initialization case
> (just a couple of lines above it), we have a
> 
>    $(call cc-option, -Wno-stringop-overflow)
> 
> thing, along with several cases in loongarch and riscv.
> 
> So they are presumably _also_ broken, but perhaps just happened to
> silently work due to compiler versions (and that stringop-overflow
> case is gated by a config option that might also have hidden it from
> people).

Indeed, there were a couple of patches that flew by recently fixing some
of those instances for that reason but I guess Masahiro may have missed
them:

https://lore.kernel.org/10b1ebd8-5d32-41a2-9454-1b40e98d5187@suse.com/
https://lore.kernel.org/4b19fae4-ba5d-45b6-ae4a-8b59c178f529@suse.com/

Cheers,
Nathan