[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250312091633.GI19424@noisy.programming.kicks-ass.net>
Date: Wed, 12 Mar 2025 10:16:33 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Ramon de C Valle <rcvalle@...gle.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Matthew Maurer <mmaurer@...gle.com>, linux-kernel@...r.kernel.org,
ojeda@...nel.org, linux-tip-commits@...r.kernel.org,
Scott Constable <scott.d.constable@...el.com>,
Ingo Molnar <mingo@...nel.org>, Kees Cook <kees@...nel.org>,
x86@...nel.org, Sami Tolvanen <samitolvanen@...gle.com>,
Alice Ryhl <aliceryhl@...gle.com>
Subject: Re: [tip: x86/core] x86/ibt: Implement FineIBT-BHI mitigation
On Tue, Mar 11, 2025 at 01:23:39PM -0700, Ramon de C Valle wrote:
> On Tue, Mar 11, 2025 at 12:41 PM Miguel Ojeda
> <miguel.ojeda.sandonis@...il.com> wrote:
> >
> > On Tue, Mar 11, 2025 at 8:09 PM Ramon de C Valle <rcvalle@...gle.com> wrote:
> > >
> > > I've submitted a PR for it:
> > > https://github.com/rust-lang/rust/pull/138368. Let me know if you're
> > > able to give it a try.
> >
> > Thanks Ramon, that was quick!
> >
> > Left a comment there and linked it -- if you meant to ask Peter, then
> > I guess it would be easiest for him to use the first nightly that has
> > it as a `-Z` flag.
> >
> > i.e. I think it is simple enough to land it as-is, especially if we
> > add the quick check I suggested.
>
> Left a note there. Let me know what you think. Yes, I guess we could
> just check the next nightly that has those changes.
The rust-log-analyzer seems to suggest the nightly build failed?
Suppose it didn't fail, where do I find it?
I normally build llvm toolchains using tc-build, but it seems rust is
not actually part of llvm?
Powered by blists - more mailing lists