From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Borislav Petkov <bp@kernel.org>
Cc: X86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
stable@kernel.org, Rik van Riel <riel@surriel.com>
Subject: Re: [PATCH] x86/CPU/AMD: Fix AMD TLBI Erratum #1718
Date: Sat, 3 Oct 2026 22:24:40 +0100 [thread overview]
Message-ID: <asFqr9OEdRqCJKWj@gremlin> (raw)
In-Reply-To: <20261002211617.1001617-1-bp@kernel.org>
+cc Rik FYI!
On Fri, Oct 02, 2026 at 02:16:17PM -0700, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
>
> The processor may fail to invalidate a TLB entry while executing an
> INVLPGB/TLBSYNC instruction pair.
Hi,
I've repro'd the issue on a threadripper - a Ryzen Threadripper 9980X
(family 0x1a model 0x08 stepping 1) on microcode 0x0b008121 (the latest I
believe).
It failed Matt's repro in seconds on 7.2.7 (round 3 on the first run, round
1 on the second, same stale-offset signature Rik described).
It doesn't seem there's a microcode fix for the threadripper yet.
I confirmed tlbi=ipi fixed it, 20 rounds with no failures.
And I built and ran a kernel with this patch applied (and tlbi=ipi removed
from the kernel command line) and this patch fixes it it too - 40 rounds
with no failures.
So:
Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
Tested-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
Hopefully some useful datapoints also - + I hope there'll be a firmware fix
for the threadripper too :)
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-10-03 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 21:16 Borislav Petkov
2026-10-03 0:31 ` Rik van Riel
2026-10-03 0:44 ` Borislav Petkov
2026-10-03 21:24 ` Lorenzo Stoakes (ARM) [this message]
2026-10-03 21:44 ` Borislav Petkov
2026-10-05 17:42 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov (AMD)
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=asFqr9OEdRqCJKWj@gremlin \
--to=ljs@kernel.org \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.com \
--cc=stable@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®