From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [GIT PULL] hardening fix for v7.3-rc2
Date: Wed, 2 Sep 2026 16:49:00 -0700 [thread overview]
Message-ID: <202609021647.3F67F66B@keescook> (raw)
In-Reply-To: <CAHk-=whZQzNuBZdV1b1TBxRf+asBGtvnC=Ggu755GaOg_TYXgw@mail.gmail.com>
On Wed, Sep 02, 2026 at 04:07:46PM -0700, Linus Torvalds wrote:
> On Wed, 2 Sept 2026 at 09:31, Kees Cook <kees@kernel.org> wrote:
> >
> > - Default randstruct off with rust for better allmodconfig coverage
> > (Mark Brown)
>
> Should we just default randstruct off entirely?
>
> It defaults to off for any *real* build for good reasons. I'm not
> convinced it should be on for build testing either. Maybe the active
> compiler bugs are gone, but this whole commit is just an example of
> how RANDSTRUCT_FULL really isn't a good default - not for real life,
> and not for build test coverage.
I have a fix for it with Rust, and it'll be in -next after -rc2 is out.
We still have real-world users that depend on randstruct, so I'd like to
continue to make breakage visible via all*config builds, etc.
--
Kees Cook
next prev parent reply other threads:[~2026-09-02 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:31 [GIT PULL] hardening fix for v7.3-rc2 Kees Cook
2026-09-02 23:07 ` Linus Torvalds
2026-09-02 23:49 ` Kees Cook [this message]
2026-09-03 23:02 ` Miguel Ojeda
2026-09-04 1:38 ` Kees Cook
2026-09-04 8:12 ` Miguel Ojeda
2026-09-02 23:22 ` pr-tracker-bot
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=202609021647.3F67F66B@keescook \
--to=kees@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--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.