From: Greg KH <gregkh@linuxfoundation.org>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
stable@vger.kernel.org, Dave Hansen <dave.hansen@linux.intel.com>,
Alyssa Milburn <alyssa.milburn@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Peter Zijlstra <peterz@infradead.org>,
Dave Hansen <dave.hansen@intel.com>,
Sean Christopherson <seanjc@google.com>,
Nikolay Borisov <nik.borisov@suse.com>
Subject: Re: [PATCH 6.1.y 0/6] Delay VERW - 6.1.y backport
Date: Tue, 27 Feb 2024 10:09:06 +0100 [thread overview]
Message-ID: <2024022716-undiluted-donor-17cb@gregkh> (raw)
In-Reply-To: <20240227085638.plb5gvunrjqgj7yp@desk>
On Tue, Feb 27, 2024 at 12:56:38AM -0800, Pawan Gupta wrote:
> On Tue, Feb 27, 2024 at 09:21:33AM +0100, Jiri Slaby wrote:
> > On 27. 02. 24, 9:00, Pawan Gupta wrote:
> > > This is the backport of recently upstreamed series that moves VERW
> > > execution to a later point in exit-to-user path. This is needed because
> > > in some cases it may be possible for data accessed after VERW executions
> > > may end into MDS affected CPU buffers. Moving VERW closer to ring
> > > transition reduces the attack surface.
> > >
> > > Patch 1/6 includes a minor fix that is queued for upstream:
> > > https://lore.kernel.org/lkml/170899674562.398.6398007479766564897.tip-bot2@tip-bot2/
> >
> > Ah, you note it here.
> >
> > But you should include this patch on its own instead of merging it to 1/6.
>
> Thats exactly what I would have done ideally, but the backports to
> stable kernels < 6.6 wont work without this patch. And this patch is
> going to take some time before it can be merged upstream.
It's in the tip-urgent branch, doesn't that mean it will go to Linus
this week? If it's in linux-next, and you _KNOW_ it will go to Linus
this week, and the git id is stable, then we can consider the
application of it to the stable tree now.
But if it's not working for anyone without this change (i.e. in Linus's
branch), why would you want these changes in a stable tree?
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-27 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 8:00 [PATCH 6.1.y 0/6] Delay VERW - 6.1.y backport Pawan Gupta
2024-02-27 8:00 ` [PATCH 6.1.y 1/6] x86/bugs: Add asm helpers for executing VERW Pawan Gupta
2024-02-27 8:19 ` Jiri Slaby
2024-02-27 8:40 ` Pawan Gupta
2024-02-27 8:00 ` [PATCH 6.1.y 2/6] x86/entry_64: Add VERW just before userspace transition Pawan Gupta
2024-02-27 8:00 ` [PATCH 6.1.y 3/6] x86/entry_32: " Pawan Gupta
2024-02-27 8:00 ` [PATCH 6.1.y 4/6] x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key Pawan Gupta
2024-02-27 8:00 ` [PATCH 6.1.y 5/6] KVM/VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH Pawan Gupta
2024-02-27 8:00 ` [PATCH 6.1.y 6/6] KVM/VMX: Move VERW closer to VMentry for MDS mitigation Pawan Gupta
2024-02-27 8:21 ` [PATCH 6.1.y 0/6] Delay VERW - 6.1.y backport Jiri Slaby
2024-02-27 8:56 ` Pawan Gupta
2024-02-27 9:09 ` Greg KH [this message]
2024-02-29 9: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=2024022716-undiluted-donor-17cb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alyssa.milburn@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=nik.borisov@suse.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--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