All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nikolay Borisov <nik.borisov@suse.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2 0/7] 5.4 backport of recent mds improvement patches
Date: Mon, 26 Feb 2024 14:30:50 +0100	[thread overview]
Message-ID: <2024022603-speculate-staple-4f54@gregkh> (raw)
In-Reply-To: <20240226122237.198921-1-nik.borisov@suse.com>

On Mon, Feb 26, 2024 at 02:22:30PM +0200, Nikolay Borisov wrote:
> Here's the recently merged mds improvement patches adapted to latest stable tree.
> I've only compile tested them, but since I have also done similar backports for
> older kernels I'm sure they should work.
> The main difference is in the definition of the CLEAR_CPU_BUFFERS macro since
> 5.4 doesn't contains the alternative relocation handling logic hence the verw
> instruction is moved out of the alternative definition and instead we have a jump which
> skips the verw instruction there. That way the relocation will be handled by the
> toolchain rather than the kernel.
> 
> Since I don't know if I will have time to work on the other branches this patchset
> can be used as basis for the rest of the stable kernels. The main difference would be
> which bit is used for CLEAR_CPU_BUFFERS. For kernel 6.6 the 2nd patch can be used verbatim
> from upstrem (unlike this modified version) since the alternative relocation
> did land in v6.5. However, even if used as-is from this patchset it's not a problem.

As mentioned on IRC, I can't take these now, without the newer branches
fixed first, otherwise someone could upgrade and have a regression.

So I'll hold off on these until we backports for all of the other stable
trees as well.

thanks,

greg k-h

      parent reply	other threads:[~2024-02-26 13:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 12:22 [PATCH v2 0/7] 5.4 backport of recent mds improvement patches Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 1/7] x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix Nikolay Borisov
2024-03-12  1:33   ` Pawan Gupta
2024-03-12  5:57     ` Nikolay Borisov
2024-03-29 12:46       ` Greg KH
2024-02-26 12:22 ` [PATCH v2 2/7] x86/bugs: Add asm helpers for executing VERW Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 3/7] x86/entry_64: Add VERW just before userspace transition Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 4/7] x86/entry_32: " Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 5/7] x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 6/7] KVM/VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 7/7] KVM/VMX: Move VERW closer to VMentry for MDS mitigation Nikolay Borisov
2024-02-26 13:30 ` Greg KH [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=2024022603-speculate-staple-4f54@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=nik.borisov@suse.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 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.