From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Mark Brown" <broonie@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Günther Noack" <gnoack@google.com>,
"Arnd Bergmann" <arnd@arndb.de>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] gcc-plugins: Disable GCC plugins for compile test builds
Date: Wed, 9 Apr 2025 10:46:00 -0700 [thread overview]
Message-ID: <202504091044.D789172C@keescook> (raw)
In-Reply-To: <CAHk-=whKEuQQh2JymabBQLrLs=pEfx0qYVmUnYZRq_tOFj90sA@mail.gmail.com>
On Wed, Apr 09, 2025 at 10:42:19AM -0700, Linus Torvalds wrote:
> On Wed, 9 Apr 2025 at 10:29, Mark Brown <broonie@kernel.org> wrote:
> >
> > 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 wouldn't be entirely surpised if a lot of the build bots end up
> running old distros (because "enterprise").
>
> So this is presumably only happening with certain compiler versions,
> and I expect the build bots have a fairly small set of compilers they
> end up testing.
I'm still trying to figure out what the matrix is, because I can
reproduce the crash on Debian's GCC 12 but not Ubuntu's GCC 13, etc.
It feels like there are a few corner cases involved here. So it's
not just the regular "new compiler changes" that usually break the
plugins. Regardless, I'm still digging...
--
Kees Cook
next prev parent reply other threads:[~2025-04-09 17:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 20:57 [PATCH] gcc-plugins: Disable GCC plugins for compile test builds Mark Brown
2025-04-07 21:33 ` Linus Torvalds
2025-04-07 22:02 ` Mark Brown
2025-04-08 9:22 ` Arnd Bergmann
2025-04-08 20:37 ` Kees Cook
2025-04-10 7:58 ` Arnd Bergmann
2025-04-08 23:32 ` Kees Cook
2025-04-09 5:43 ` Arnd Bergmann
2025-04-09 12:19 ` Mark Brown
2025-04-09 15:33 ` Linus Torvalds
2025-04-09 17:29 ` Mark Brown
2025-04-09 17:42 ` Linus Torvalds
2025-04-09 17:46 ` Kees Cook [this message]
2025-04-09 18:09 ` Mark Brown
2025-04-09 19:24 ` Arnd Bergmann
2025-04-15 20:26 ` Palmer Dabbelt
2025-04-15 20:41 ` Mark Brown
2025-04-15 20:43 ` Kees Cook
2025-04-15 20:41 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202504091044.D789172C@keescook \
--to=kees@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=gnoack@google.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.