public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: 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.6.y 0/6] Delay VERW - 6.6.y backport
Date: Tue, 27 Feb 2024 09:54:00 +0100	[thread overview]
Message-ID: <2024022740-smugness-cone-e80c@gregkh> (raw)
In-Reply-To: <20240226-delay-verw-backport-6-6-y-v1-0-aa17b2922725@linux.intel.com>

On Mon, Feb 26, 2024 at 09:34:14PM -0800, 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/

Obviously I can't take this, you know that :(

Please include the actual commit in the series, when it hits Linus's
tree.

I'm dropping all of these backports from my review queue, please resend
the fixed up series when they are ready.

thanks,

greg k-h

  parent reply	other threads:[~2024-02-27  8:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27  5:34 [PATCH 6.6.y 0/6] Delay VERW - 6.6.y backport Pawan Gupta
2024-02-27  5:34 ` [PATCH 6.6.y 1/6] x86/bugs: Add asm helpers for executing VERW Pawan Gupta
2024-02-27  5:34 ` [PATCH 6.6.y 2/6] x86/entry_64: Add VERW just before userspace transition Pawan Gupta
2024-02-27  5:34 ` [PATCH 6.6.y 3/6] x86/entry_32: " Pawan Gupta
2024-02-27  5:34 ` [PATCH 6.6.y 4/6] x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key Pawan Gupta
2024-02-27  5:34 ` [PATCH 6.6.y 5/6] KVM/VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH Pawan Gupta
2024-02-27  5:34 ` [PATCH 6.6.y 6/6] KVM/VMX: Move VERW closer to VMentry for MDS mitigation Pawan Gupta
2024-02-27  8:54 ` Greg KH [this message]
2024-02-27  9:05   ` [PATCH 6.6.y 0/6] Delay VERW - 6.6.y backport Pawan Gupta
2024-02-27  9:10     ` Greg KH

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=2024022740-smugness-cone-e80c@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=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