[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202502061039.A75818BA@keescook>
Date: Thu, 6 Feb 2025 10:48:27 -0800
From: Kees Cook <kees@...nel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: "Justin M. Forbes" <jforbes@...oraproject.org>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add -fzero-init-padding-bits to bindgen_skip_cflags
On Thu, Feb 06, 2025 at 04:55:21PM +0100, Miguel Ojeda wrote:
> On Thu, Feb 6, 2025 at 4:45 PM Kees Cook <kees@...nel.org> wrote:
> >
> > Thanks for this! I keep forgetting to keep flags in sync. I wonder if
> > there is a way to automate some kind of warning for this (even when
> > CONFIG_RUST=n)?
>
> You mean at editing time?
>
> > Reviewed-by: Kees Cook <kees@...nel.org>
>
> Thanks! I will add it.
>
> > Miguel, I see you took this already -- is it planned to land for -rc2?
>
> Possibly, depends on how it goes; otherwise -rc3 -- why?
Many subsystems base their trees on -rc2, so if it missed rc2, Rust builds
in a given subsystem will be broken under gcc 15 (but fine in -next).
But perhaps that's enough of a corner case that it doesn't matter? I
have other fixes I'm sending to Linus tomorrow, if you'd rather it go in
sooner? I'm fine either way. :)
--
Kees Cook
Powered by blists - more mailing lists