linux-kernel - Re: [PATCH] gcc-plugins: Disable GCC plugins for compile test builds

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: <a9a459c2-674d-43dc-9e27-41de0471f602@sirena.org.uk>
Date: Wed, 9 Apr 2025 18:29:10 +0100
From: Mark Brown <broonie@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Kees Cook <kees@...nel.org>,
	Mickaël Salaün <mic@...ikod.net>,
	Günther Noack <gnoack@...gle.com>,
	Arnd Bergmann <arnd@...db.de>, linux-hardening@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [PATCH] gcc-plugins: Disable GCC plugins for compile test builds

On Wed, Apr 09, 2025 at 08:33:03AM -0700, Linus Torvalds wrote:
> On Wed, 9 Apr 2025 at 05:20, Mark Brown <broonie@...nel.org> wrote:

> > Note that the patch is only disabling for build coverage builds where
> > the resulting binaries generally aren't going to actually be run.

> Well, there's a reason we do build coverage - we also want to test
> that the non-build coverage case builds.

> And it's not actually obvious that it does - it's in fact rather
> likely that the gcc plugin is broken in general, and it just so
> happens that it's the build bots that find it.

Sadly it seems like the build bots didn't find it, or at least if they
found it they didn't identify it well enough to end up with reporting
the issue to someone who'd fix it.  I ran into it because I do
allmodconfig builds as part of applying things since both you and
Stephen do them and that exploded in my face at -rc1.

> Which is why I honestly would prefer to just disable the plugins in general.

> Because the problem is the plugin, not the build coverage.

Well, yes.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)