From: Jiaqing Zhao <Zhao.Jiaqing@amd.com>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Penny Zheng <penny.zheng@amd.com>,
x86@kernel.org, ray.huang@amd.com, Jason.Andryuk@amd.com,
stefano.stabellini@amd.com,
Mario Limonciello <mario.limonciello@amd.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] x86/amd_node: harden amd_smn_init() against Xen dom0 topology
Date: Tue, 2 Jun 2026 13:28:16 +0800 [thread overview]
Message-ID: <c4ecc349-2f93-40aa-965f-9fe57c3f0f4f@amd.com> (raw)
In-Reply-To: <20260519141002.GA369920@yaz-khff2.amd.com>
Hi, Yazen
On 2026-05-19 22:10, Yazen Ghannam wrote:
> On Thu, May 07, 2026 at 04:37:43PM +0800, Jiaqing Zhao wrote:
>> This amd_smn_init div0 oops is also observed on 6.19.14+deb14 (Debian testing)
>> and 6.18.27. Given that 6.18 is LTS, suggesting `Cc: stable@vger.kernel.org`
>> to get it backported.
>>
>
> Hi Jiaqing,
>
> So is the issue observed with the latest mainline kernel?
>
> Or only with v6.19 and before?
It is observed with both latest mainline and v6.18/6.19. The issue comes with
commit 0a4b61d9c2e49 ("x86/amd_node: Fix AMD root device caching").
Thanks,
Jiaqing
> Thanks,
> Yazen
next prev parent reply other threads:[~2026-06-02 5:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 5:55 Penny Zheng
2026-05-06 5:55 ` [PATCH v1 1/2] x86/amd_node: avoid divide-by-zero in amd_smn_init() under Xen dom0 Penny Zheng
2026-05-06 5:55 ` [PATCH v1 2/2] x86/amd_node: reject SMN access when amd_smn_init() did not complete Penny Zheng
2026-05-06 17:17 ` [PATCH v1 0/2] x86/amd_node: harden amd_smn_init() against Xen dom0 topology Mario Limonciello
2026-05-07 8:37 ` Jiaqing Zhao
2026-05-19 14:10 ` Yazen Ghannam
2026-06-02 5:28 ` Jiaqing Zhao [this message]
2026-06-02 18:48 ` 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=c4ecc349-2f93-40aa-965f-9fe57c3f0f4f@amd.com \
--to=zhao.jiaqing@amd.com \
--cc=Jason.Andryuk@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=penny.zheng@amd.com \
--cc=ray.huang@amd.com \
--cc=stefano.stabellini@amd.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yazen.ghannam@amd.com \
/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®