From: Kees Cook <kees@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
mic@digikod.net, 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: Tue, 15 Apr 2025 13:43:03 -0700 [thread overview]
Message-ID: <202504151342.7362AD8817@keescook> (raw)
In-Reply-To: <2a4a73bc-03a7-4bac-9d56-dad85df3e1b8@sirena.org.uk>
On Tue, Apr 15, 2025 at 09:41:06PM +0100, Mark Brown wrote:
> On Tue, Apr 15, 2025 at 01:26:34PM -0700, Palmer Dabbelt wrote:
> > On Mon, 07 Apr 2025 13:57:32 PDT (-0700), broonie@kernel.org wrote:
>
> > > In current mainline x86_64 allmodconfig builds done with tuxmake GCC 13
> > > and GCC 14 toolchains (which are Debian ones packaged up into containers)
> > > generate ICEs in landlock:
>
> > This one's been biting me too. It manifests for me on gcc-12 and gcc-13
> > (both locally built toolchains off the release branches, cross compiling for
> > RISC-V).
>
> > Tested-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> Kees has a narrower workaround for this:
>
> https://lore.kernel.org/all/20250409151154.work.872-kees@kernel.org/
>
> It's in -next but not pending-fixes, I'm not sure what the plan is for
> getting this into mainline - Kees? The commit log mentions getting it
> in for -rc2 so I think the plan is to merge it as a fix.
Yeah, I missed -rc2, and will send it to Linus for -rc3 (with other
stuff) probably tomorrow.
--
Kees Cook
next prev parent reply other threads:[~2025-04-15 20:43 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
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 [this message]
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=202504151342.7362AD8817@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=palmer@dabbelt.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox