Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "S Shaiju (AMD)" <sshaiju.lkml@gmail.com>
Cc: stable@vger.kernel.org, bp@alien8.de
Subject: Re: [PATCH 6.18] x86/bugs: Adapt SRSO mitigation to Zen6
Date: Wed, 4 Nov 2026 12:58:23 -0500	[thread overview]
Message-ID: <2026110405-exporter-surfacing-9624@gregkh> (raw)
In-Reply-To: <20261103182143.27403-1-sshaiju.lkml@gmail.com>

On Tue, Nov 03, 2026 at 10:21:43AM -0800, S Shaiju (AMD) wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> 
> commit ae1d2082d93bc04604dc08e9b7f9cdba5e0c28e6 upstream.
> 
> Zen6 has BTB protection which isolates the different contexts
> (user/kernel, guest/host) from one another. This makes the SafeRET
> mitigation there unnecessary leaving the user/user and guest/guest
> attack vectors open, whose protection is handled by the Spectre v2
> mitigation setting to do IBPB on a context switch.
> 
> Detect that setting and report it with a new mitigation string.
> 
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> Link: https://patch.msgid.link/20260822013231.1109255-1-bp@kernel.org
> Signed-off-by: S Shaiju (AMD) <sshaiju.lkml@gmail.com>
> ---
>  arch/x86/include/asm/cpufeatures.h |  1 +
>  arch/x86/kernel/cpu/bugs.c         | 18 ++++++++++++++++--
>  arch/x86/kernel/cpu/scattered.c    |  1 +
>  3 files changed, 18 insertions(+), 2 deletions(-)

You forgot to mention this needs to go to 7.3.y too.

Now queued up, thanks.

greg k-h

  parent reply	other threads:[~2026-11-04 17:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 18:21 [PATCH 6.18] x86/bugs: Adapt SRSO mitigation to Zen6 S Shaiju (AMD)
2026-11-04 15:03 ` Sasha Levin
2026-11-04 16:40   ` Borislav Petkov
2026-11-04 17:58 ` Greg KH [this message]
2026-11-04 21:08   ` Borislav Petkov
2026-11-04 21:19     ` Greg KH
2026-11-05  2:17       ` Borislav Petkov

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=2026110405-exporter-surfacing-9624@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bp@alien8.de \
    --cc=sshaiju.lkml@gmail.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