From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: stable@vger.kernel.org, Thomas Voegtle <tv@lio96.de>,
kim.phillips@amd.com
Subject: Re: [PATCH 5.15-stable] x86/CPU/AMD: Properly check the TSA microcode
Date: Sat, 12 Jul 2025 14:04:04 +0200 [thread overview]
Message-ID: <2025071253-perfectly-geography-c56f@gregkh> (raw)
In-Reply-To: <20250711194558.GLaHFp9kw1s5dSmBUa@fat_crate.local>
On Fri, Jul 11, 2025 at 09:45:58PM +0200, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> Date: Fri, 11 Jul 2025 17:40:18 +0200
>
> In order to simplify backports, I resorted to an older version of the
> microcode revision checking which didn't pull in the whole struct
> x86_cpu_id matching machinery.
>
> My simpler method, however, forgot to add the extended CPU model to the
> patch revision, which lead to mismatches when determining whether TSA
> mitigation support is present.
>
> So add that forgotten extended model.
>
> Also, fix a backport mismerge which put tsa_init() where it doesn't
> belong.
>
> This is a stable-only fix and the preference is to do it this way
> because it is a lot simpler. Also, the Fixes: tag below points to the
> respective stable patch.
>
> Fixes: 90293047df18 ("x86/bugs: Add a Transient Scheduler Attacks mitigation")
> Reported-by: Thomas Voegtle <tv@lio96.de>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> Tested-by: Thomas Voegtle <tv@lio96.de>
> Message-ID: <04ea0a8e-edb0-c59e-ce21-5f3d5d167af3@lio96.de>
> ---
> arch/x86/kernel/cpu/amd.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
All now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2025-07-12 12:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 12:03 TSA mitigation doesn't work on 6.6.y Thomas Voegtle
2025-07-11 12:25 ` Borislav Petkov
2025-07-11 13:15 ` Thomas Voegtle
2025-07-11 15:35 ` Borislav Petkov
2025-07-11 16:03 ` Thomas Voegtle
2025-07-11 16:44 ` Borislav Petkov
2025-07-11 16:56 ` Thomas Voegtle
2025-07-11 17:41 ` Borislav Petkov
2025-07-11 18:11 ` Thomas Voegtle
2025-07-11 18:15 ` Borislav Petkov
2025-07-11 19:18 ` [PATCH 6.12-stable] x86/CPU/AMD: Properly check the TSA microcode Borislav Petkov
2025-07-13 13:05 ` Sasha Levin
2025-07-11 19:23 ` [PATCH 6.6-stable] " Borislav Petkov
2025-07-13 13:30 ` Sasha Levin
2025-07-11 19:30 ` [PATCH 6.1-stable] " Borislav Petkov
2025-07-13 13:06 ` Sasha Levin
2025-07-11 19:45 ` [PATCH 5.15-stable] " Borislav Petkov
2025-07-12 12:04 ` Greg KH [this message]
2025-07-13 13:06 ` Sasha Levin
2025-07-13 16:10 ` Borislav Petkov
2025-07-14 1:50 ` Sasha Levin
2025-07-14 10:28 ` Borislav Petkov
2025-07-14 16:30 ` Sasha Levin
2025-07-14 16:33 ` 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=2025071253-perfectly-geography-c56f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=kim.phillips@amd.com \
--cc=stable@vger.kernel.org \
--cc=tv@lio96.de \
/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.