From: Kees Cook <kees@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Justin M. Forbes" <jforbes@fedoraproject.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add -fzero-init-padding-bits to bindgen_skip_cflags
Date: Thu, 6 Feb 2025 10:48:27 -0800 [thread overview]
Message-ID: <202502061039.A75818BA@keescook> (raw)
In-Reply-To: <CANiq72meqUFt136PQt=h6b5p+wJ5KvdYM2ci_QNKbHaR2wY71A@mail.gmail.com>
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@kernel.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@kernel.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
next prev parent reply other threads:[~2025-02-06 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 21:50 [PATCH] Add -fzero-init-padding-bits to bindgen_skip_cflags Justin M. Forbes
2025-02-05 23:18 ` Miguel Ojeda
2025-02-06 15:45 ` Kees Cook
2025-02-06 15:55 ` Miguel Ojeda
2025-02-06 18:48 ` Kees Cook [this message]
2025-02-06 18:58 ` Miguel Ojeda
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=202502061039.A75818BA@keescook \
--to=kees@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=jforbes@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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.