From: Jason Andryuk <jason.andryuk@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Thomas Gleixner <tglx@kernel.org>, <x86@kernel.org>,
Yazen Ghannam <yazen.ghannam@amd.com>,
<linux-kernel@vger.kernel.org>, Penny Zheng <penny.zheng@amd.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] x86/amd_node: Avoid divide by zero on virtualized systems
Date: Tue, 25 Aug 2026 10:10:48 -0400 [thread overview]
Message-ID: <4b253fa1-1d2e-49e4-9d1a-ea4ff81d4486@amd.com> (raw)
In-Reply-To: <20260825040039.GAao0TZ6b8j0kp2RKk@fat_crate.local>
On 2026-08-25 00:00, Borislav Petkov wrote:
> On Fri, Aug 14, 2026 at 05:42:52PM -0400, Jason Andryuk wrote:
>> On a virtualized system, the number of nodes does not have a
>> relationship to the number of roots. A Xen PVH dom0 can calculate
>> roots_per_node as 0, which crashes with a divide by zero in:
>>
>> if (count++ % roots_per_node)
>>
>> The issue is seen with Xen, but it could affect other systems.
>>
>> Change roots_per_node == 0 to 1 to allow the system to boot. Print a
>> warning when this is performed for non-virtualized systems.
>>
>> Fixes: 0a4b61d9c2e4 ("x86/amd_node: Fix AMD root device caching")
>> Cc: stable@vger.kernel.org
>> Suggested-by: Borislav Petkov <bp@alien8.de>
>> Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>
>> ---
>> v2:
>> Print as a warning instead of error
>> Use "!" instead of "== 0".
>>
>> X86_FEATURE_XENPV is only for PV, but this is observed with a PVH dom0.
>> ---
>> arch/x86/kernel/amd_node.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/x86/kernel/amd_node.c b/arch/x86/kernel/amd_node.c
>> index 0be01725a2a4..c3e214925d9c 100644
>> --- a/arch/x86/kernel/amd_node.c
>> +++ b/arch/x86/kernel/amd_node.c
>> @@ -287,6 +287,11 @@ static int __init amd_smn_init(void)
>> return -ENOMEM;
>>
>> roots_per_node = num_roots / num_nodes;
>> + if (!roots_per_node) {
>> + if (!cpu_feature_enabled(X86_FEATURE_HYPERVISOR))
>> + pr_warn(FW_BUG "Error detecting roots per node.");
>> + roots_per_node = 1;
>> + }
>>
>> count = 0;
>> node = 0;
>> --
>
> https://sashiko.dev/#/patchset/20260814214255.83127-1-jason.andryuk%40amd.com
>
> And this one specifically (the other two are being addressed):
>
> "Are we missing a newline character at the end of this warning message?
> Without a trailing \n in the format string, subsequent kernel messages might
> be appended to the same line, resulting in malformed dmesg output."
Yes, thanks. I'll fix.
Regards,
Jason
next prev parent reply other threads:[~2026-08-25 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 21:42 [PATCH v2 0/2] x86/amd_node: Fixes for virtualized systems Jason Andryuk
2026-08-14 21:42 ` [PATCH v2 1/2] x86/amd_node: Avoid divide by zero on " Jason Andryuk
2026-08-24 20:05 ` Jason Andryuk
2026-08-24 21:04 ` Yazen Ghannam
2026-08-25 0:02 ` Jason Andryuk
2026-08-25 4:00 ` Borislav Petkov
2026-08-25 14:10 ` Jason Andryuk [this message]
2026-08-14 21:42 ` [PATCH v2 2/2] x86/amd_node: Remove smn_exclusive Jason Andryuk
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=4b253fa1-1d2e-49e4-9d1a-ea4ff81d4486@amd.com \
--to=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=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.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