Linux Security Modules development
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Kees Cook" <kees@kernel.org>
Cc: "Mark Brown" <broonie@kernel.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	"Paul Moore" <paul@paul-moore.com>,
	"James Morris" <jmorris@namei.org>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	linux-hardening@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	"Mickaël Salaün" <mic@digikod.net>,
	"Günther Noack" <gnoack@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hardening: Disable GCC randstruct for COMPILE_TEST
Date: Wed, 09 Apr 2025 17:22:30 +0200	[thread overview]
Message-ID: <37bccc57-01b2-46ab-b973-ad52590f4ca2@app.fastmail.com> (raw)
In-Reply-To: <20250409151154.work.872-kees@kernel.org>

On Wed, Apr 9, 2025, at 17:11, Kees Cook wrote:
> There is a GCC crash bug in the randstruct for latest GCC versions that
> is being tickled by landlock[1]. Temporarily disable GCC randstruct for
> COMPILE_TEST builds to unbreak CI systems for the coming -rc2. This can
> be restored once the bug is fixed.
>
> Suggested-by: Mark Brown <broonie@kernel.org>
> Link: 
> https://lore.kernel.org/all/20250407-kbuild-disable-gcc-plugins-v1-1-5d46ae583f5e@kernel.org/ 
> [1]
> Signed-off-by: Kees Cook <kees@kernel.org>

Acked-by: Arnd Bergmann <arnd@arndb.de>

  reply	other threads:[~2025-04-09 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 15:11 [PATCH] hardening: Disable GCC randstruct for COMPILE_TEST Kees Cook
2025-04-09 15:22 ` Arnd Bergmann [this message]
2025-04-09 15:26 ` Mark Brown

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=37bccc57-01b2-46ab-b973-ad52590f4ca2@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=gnoack@google.com \
    --cc=gustavoars@kernel.org \
    --cc=jmorris@namei.org \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.com \
    /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