From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Lance Yang <lance.yang@linux.dev>, Pedro Falcato <pfalcato@suse.de>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, tglx@kernel.org, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, hpa@zytor.com, riel@surriel.com,
linux-kernel@vger.kernel.org, qi.zheng@linux.dev,
nadav.amit@gmail.com, thomas.lendacky@amd.com,
kernel-team@meta.com, linux-mm@kvack.org,
akpm@linux-foundation.org, brendan.jackman@linux.dev,
jannh@google.com, mhklinux@outlook.com, Manali.Shukla@amd.com,
mingo@kernel.org, stable@vger.kernel.org, toshi.kani@hpe.com,
david@kernel.org, mikhail.v.gavrilov@gmail.com
Subject: Re: [PATCH 1/1] x86/mm: fix incomplete page-table invalidation with TCE
Date: Mon, 5 Oct 2026 16:22:31 +0100 [thread overview]
Message-ID: <9459bab2-b373-4008-8f3d-f84b62db5b67@citrix.com> (raw)
In-Reply-To: <6801221a-6307-407a-85fc-46906f95d22e@linux.dev>
On 05/10/2026 11:12 am, Lance Yang wrote:
> On 2026/10/5 17:57, Andrew Cooper wrote:
>> On 05/10/2026 9:32 am, Lance Yang wrote:
>>> On 2026/10/5 16:19, Andrew Cooper wrote:
>>>> On 05/10/2026 8:29 am, Lance Yang wrote:
>>>>>>
>>>>>> Did you repro any bug related to this? The functionality is perhaps
>>>>>> underspecified in the AMD manual.
>>>>>
>>>>> TBH, I don't have a reproducer yet. Just LLM stumbled upon this while
>>>>> I was investigating another memory corruption issue [1].
>>>>>
>>>>> [1]
>>>>> https://lore.kernel.org/linux-mm/arY1Wq6R9OY20ans@pcnci.linuxbox.cz/#t
>>>>>
>>>>
>>>> What hardware are you running on?
>>>>
>>>> That looks like the Zen5 issue, for which you want either the latest
>>>> microcode out of linux-firmware and/or
>>>> https://lore.kernel.org/r/20261002211617.1001617-1-bp@kernel.org
>>>>
>>>> TCE is a no-op in Zen1 and later, so unless you're on older
>>>> hardware, it
>>>> won't be that.
>>>
>>> Just to clarify ... these are two separate issues.
>>>
>>> I mentioned [1] only to explain how this came up while investigating
>>> something else. I'm not claiming that TCE caused the corruption
>>> reported
>>> there :)
>>
>> Please can you answer the question. Which CPU are you seeing this on?
>>
>
> Which CPU? None so far. As I said, I don't have a reproducer. I'm trying
> to make sense of what the manual says and what the code does ...
I'm afraid that if you're trying to be helpful, you've had entirely the
opposite effect.
TLB handling is a complicated topic. What you've done is present what
is effectively a query about the AMD manual as if it were a bugfix for
an critical-sounding issue. You even sited a real bug-report for an
actually-critical issue, despite it turning out to have nothing to do
with your submission.
The patch is buggy. For starters, you should be checking is whether TCE
is enabled, not whether it's available on the system. This causes the
more expensive option to use used even when TCE is turned off.
But, AIUI INVLPG only flushes the whole structure cache because of a
windows bug which caused it to crash on a 486. AMD deliberately
introduced TCE to remove this overhead for every OS which didn't want
lumbering with a workaround for buggy windows.
Linux currently believes that it's TLB invalidation algorithm is
compatible with TCE, so at a bare minimum, you need to have some kind of
discussion on why you believe this not to be true before claiming that
it "might be unsafe because the manual says so".
It's fine to ask a question, and even ask "so shouldn't the code look
like this?" but such a patch needs a very clear RFC or QUESTION tag.
~Andrew
next prev parent reply other threads:[~2026-10-05 15:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 5:23 Lance Yang
2026-10-05 5:47 ` Andrew Morton
2026-10-05 6:09 ` Pedro Falcato
2026-10-05 7:29 ` Lance Yang
2026-10-05 8:19 ` Andrew Cooper
2026-10-05 8:32 ` Lance Yang
2026-10-05 9:57 ` Andrew Cooper
2026-10-05 10:12 ` Lance Yang
2026-10-05 14:22 ` Borislav Petkov
2026-10-05 14:36 ` Lance Yang
2026-10-05 14:53 ` Borislav Petkov
2026-10-05 14:58 ` Lance Yang
2026-10-05 15:22 ` Andrew Cooper [this message]
2026-10-05 15:36 ` Lance Yang
2026-10-05 10:24 ` Pedro Falcato
2026-10-05 12:10 ` Lance Yang
2026-10-05 6:38 ` Nadav Amit
2026-10-05 7:23 ` Lance Yang
2026-10-05 15:15 ` Rik van Riel
2026-10-05 15:30 ` Lance Yang
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=9459bab2-b373-4008-8f3d-f84b62db5b67@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Manali.Shukla@amd.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=brendan.jackman@linux.dev \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=kernel-team@meta.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mhklinux@outlook.com \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=peterz@infradead.org \
--cc=pfalcato@suse.de \
--cc=qi.zheng@linux.dev \
--cc=riel@surriel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=toshi.kani@hpe.com \
--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®