[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250410135713.GG9833@noisy.programming.kicks-ass.net>
Date: Thu, 10 Apr 2025 15:57:13 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Paweł Anikiel <panikiel@...gle.com>,
Sami Tolvanen <samitolvanen@...gle.com>,
Kees Cook <kees@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Alice Ryhl <aliceryhl@...gle.com>,
Nathan Chancellor <nathan@...nel.org>, x86@...nel.org,
linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH] x86/Kconfig: make CFI_AUTO_DEFAULT depend on !RUST
On Thu, Apr 10, 2025 at 03:54:32PM +0200, Miguel Ojeda wrote:
> On Thu, Apr 10, 2025 at 3:34 PM Peter Zijlstra <peterz@...radead.org> wrote:
> >
> > Anyway, given this core nonsense is now CFI unsound, it is no longer
> > suitable to build the kernel. So either refrain from using part of the
> > core that trips this, or get it fixed asap.
>
> We discussed it a bit yesterday. Still, until it gets resolved one way
> or another, we should be avoiding people to build the kernel like
> that, no?
Remove the offending Rust code? Afaict from this github issue, it is
just some formatting nonsense. Surely code can be adjusted to not use
that?
Powered by blists - more mailing lists