linux-kernel - Re: [PATCH] x86/Kconfig: make CFI_AUTO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250410132649.GE9833@noisy.programming.kicks-ass.net>
Date: Thu, 10 Apr 2025 15:26:49 +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:21:44PM +0200, Miguel Ojeda wrote:
> On Thu, Apr 10, 2025 at 3:09 PM Peter Zijlstra <peterz@...radead.org> wrote:
> >
> > Miguel, I cannot find this code in the kernel tree. Is this again
> > because Rust is not free-standing and relies on external code?
> 
> Yes, this comes from the `core` standard library. If it requires a
> change, then it needs to be fixed upstream.
> 
> > Can you please fix that. Building against external code that is not
> > under our control is a problem.
> 
> The only way to fix it would be to vendor the standard library, for
> each Rust compiler version -- and there is one new every 6 weeks.
> Thus, quite a few copies of it. Or keep patches (one per version) that
> we apply on the fly.

New compiler can't build old core?