From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Kees Cook <kees@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [tip: x86/cpu] x86/kcfi: Require FRED for FineIBT
Date: Fri, 21 Feb 2025 22:15:27 +0100 [thread overview]
Message-ID: <Z7js71Q8Fl2E8mt7@gmail.com> (raw)
In-Reply-To: <20250221190236.GD7373@noisy.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Fri, Feb 21, 2025 at 08:00:24PM +0100, Peter Zijlstra wrote:
> > On Fri, Feb 21, 2025 at 03:08:05PM -0000, tip-bot2 for Kees Cook wrote:
> > > The following commit has been merged into the x86/cpu branch of tip:
> > >
> > > Commit-ID: f12315780faf1cbfe00991077a1e8c8e4c201f3b
> > > Gitweb: https://git.kernel.org/tip/f12315780faf1cbfe00991077a1e8c8e4c201f3b
> > > Author: Kees Cook <kees@kernel.org>
> > > AuthorDate: Fri, 14 Feb 2025 11:22:21 -08:00
> > > Committer: Ingo Molnar <mingo@kernel.org>
> > > CommitterDate: Fri, 21 Feb 2025 15:38:11 +01:00
> >
> > Ingo, seriously NO!
>
> I've zapped the commit.
I've also re-integrated tip:master to make sure it doesn't go out to -next.
Sorry about that ...
Thanks,
Ingo
prev parent reply other threads:[~2025-02-21 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 19:22 [PATCH] x86/kcfi: Require FRED for FineIBT Kees Cook
2025-02-14 19:39 ` Andrew Cooper
2025-02-14 21:54 ` Kees Cook
2025-02-14 22:40 ` Andrew Cooper
2025-02-16 23:52 ` Kees Cook
2025-02-21 15:08 ` [tip: x86/cpu] " tip-bot2 for Kees Cook
2025-02-21 19:00 ` Peter Zijlstra
2025-02-21 19:02 ` Peter Zijlstra
2025-02-21 21:15 ` Ingo Molnar [this message]
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=Z7js71Q8Fl2E8mt7@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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.