From: Greg KH <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: peterz@infradead.org, stable@vger.kernel.org,
Daniel Sneddon <daniel.sneddon@linux.intel.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Borislav Petkov <bp@suse.de>
Subject: Re: FAILED: patch "[PATCH] x86/nospec: Fix i386 RSB stuffing" failed to apply to 5.10-stable tree
Date: Tue, 6 Sep 2022 14:07:37 +0200 [thread overview]
Message-ID: <Yxc4CeyDS2tWLXfo@kroah.com> (raw)
In-Reply-To: <ff8d3521a32e1a425af32711856d0d8fdfa84d2b.camel@decadent.org.uk>
On Fri, Sep 02, 2022 at 04:26:57PM +0200, Ben Hutchings wrote:
> On Thu, 2022-09-01 at 11:43 +0200, Greg KH wrote:
> > On Mon, Aug 29, 2022 at 04:04:58PM +0200, Ben Hutchings wrote:
> > > On Mon, 2022-08-29 at 10:30 +0200, gregkh@linuxfoundation.org wrote:
> > > > The patch below does not apply to the 5.10-stable tree.
> > > > If someone wants it applied there, or to any other stable or longterm
> > > > tree, then please email the backport, including the original git commit
> > > > id to <stable@vger.kernel.org>.
> > > >
> > >
> > > You need commit 4e3aa9238277 "x86/nospec: Unwreck the RSB stuffing"
> > > before this one. I've attached the backport of that for 5.10. I
> > > haven't checked the older branches.
> >
> > Great, thanks, this worked. But the backport did not apply to 4.19, so
> > I will need that in order to take this one as well.
>
> I've had a look at 5.4, and it's sufficiently different from upstream
> that I don't see how to move forward.
>
> However, I also found that the PBRSB mitigation seems broken, as commit
> fc02735b14ff "KVM: VMX: Prevent guest RSB poisoning attacks with eIBRS"
> was not backported (and would be hard to add).
>
> So, perhaps it would be best to revert the backports of:
>
> 2b1299322016 x86/speculation: Add RSB VM Exit protections
> ba6e31af2be9 x86/speculation: Add LFENCE to RSB fill sequence
>
> in stable branches older than 5.10.
Why? Is it because they do not work at all there, or are they causing
problems?
thanks,
greg k-h
next prev parent reply other threads:[~2022-09-06 12:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 8:30 FAILED: patch "[PATCH] x86/nospec: Fix i386 RSB stuffing" failed to apply to 5.10-stable tree gregkh
2022-08-29 14:04 ` Ben Hutchings
2022-09-01 9:43 ` Greg KH
2022-09-02 14:26 ` Ben Hutchings
2022-09-06 12:07 ` Greg KH [this message]
2022-09-06 17:07 ` Ben Hutchings
2022-09-06 21:20 ` Pawan Gupta
2022-09-07 0:23 ` Ben Hutchings
2022-09-08 6:09 ` Pawan Gupta
2022-09-08 12:44 ` Ben Hutchings
2022-09-11 5:47 ` Greg KH
2022-09-12 21:56 ` Pawan Gupta
2022-09-13 11:27 ` Greg KH
2022-09-13 0:53 ` Pawan Gupta
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=Yxc4CeyDS2tWLXfo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben@decadent.org.uk \
--cc=bp@suse.de \
--cc=daniel.sneddon@linux.intel.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox