mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	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: Thu, 03 Sep 2026 18:38:02 -0700	[thread overview]
Message-ID: <153F0BB6-98A2-4F53-BE82-16385BF01760@kernel.org> (raw)
In-Reply-To: <CANiq72=7msFj95ZYf5u5MfODci3J__KRxYEjZRL5Jj4gVyssLQ@mail.gmail.com>



On September 3, 2026 4:02:57 PM PDT, Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
>On Thu, Sep 3, 2026 at 1:49 AM Kees Cook <kees@kernel.org> wrote:
>>
>> 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.
>
>Do you mean the ones we discussed in the past like e.g. my
>
>  https://lore.kernel.org/rust-for-linux/20260323130224.165738-1-ojeda@kernel.org/
>
>or your
>
>  https://lore.kernel.org/rust-for-linux/202512092319.ECBB8613@keescook/

Yes, this latter one. I was going to send it after rc2 and we could let it bake for the whole dev cycle.

-Kees

-- 
Kees Cook

  reply	other threads:[~2026-09-04  1:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 16:31 Kees Cook
2026-09-02 23:07 ` Linus Torvalds
2026-09-02 23:49   ` Kees Cook
2026-09-03 23:02     ` Miguel Ojeda
2026-09-04  1:38       ` Kees Cook [this message]
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=153F0BB6-98A2-4F53-BE82-16385BF01760@kernel.org \
    --to=kees@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®