From: sashiko-bot@kernel.org
To: "tip-bot2 for Juergen Gross" <tip-bot2@linutronix.de>
Cc: linux-pci@vger.kernel.org
Subject: Re: [tip: x86/msr] x86/pci: Stop using 32-bit MSR interfaces
Date: Thu, 02 Jul 2026 10:25:26 +0000 [thread overview]
Message-ID: <20260702102527.2EF5C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <178298736191.3843924.4213710231240809260.tip-bot2@tip-bot2>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Calculation of the segment address overflows when the number of bus bits causes `i` to reach 8 or more.
--
commit 67dc02af5b380e39ab1fd3fd3aa7e4552b01de23
Author: Juergen Gross <jgross@suse.com>
Subject: x86/pci: Stop using 32-bit MSR interfaces
This commit replaces the 32-bit rdmsr_safe() MSR interface with the 64-bit
variant rdmsrq_safe() in the AMD Family 10h PCI MMConfig initialization
code. This simplifies the logic by directly fetching the 64-bit MSR value.
Link: https://patch.msgid.link/20260629060526.3638272-12-jgross@suse.com
> diff --git a/arch/x86/pci/mmconfig-shared.c b/arch/x86/pci/mmconfig-shared.c
> --- a/arch/x86/pci/mmconfig-shared.c
> +++ b/arch/x86/pci/mmconfig-shared.c
[ ... ]
> @@ -198,13 +198,9 @@ static const char *__init pci_mmcfg_amd_fam10h(void)
> return NULL;
>
> address = MSR_FAM10H_MMIO_CONF_BASE;
> - if (rdmsr_safe(address, &low, &high))
> + if (rdmsrq_safe(address, &msr))
> return NULL;
>
> - msr = high;
> - msr <<= 32;
> - msr |= low;
> -
> /* ECAM is not enabled */
> if (!(msr & FAM10H_MMIO_CONF_ENABLE))
> return NULL;
[ ... ]
> end_bus = (1 << busnbits) - 1;
> for (i = 0; i < (1 << segnbits); i++)
> if (pci_mmconfig_add(i, 0, end_bus,
> base + (1<<28) * i) == NULL) {
[Severity: High]
This isn't a bug introduced by this patch, but does this calculation overflow
when i reaches 8 or more in pci_mmcfg_amd_fam10h()?
The expression (1<<28) * i uses 32-bit signed arithmetic. When i >= 8, the
result reaches 2147483648, which exceeds INT_MAX and overflows to -2147483648.
Because base is a 64-bit value, this negative number will be sign-extended
and subtracted from the base instead of added to it.
If busnbits from the MSR is 12 or greater, segnbits will be 4 or more,
allowing the loop variable i to reach 8 and trigger this overflow.
--
Sashiko AI review · https://sashiko.dev/#/patchset/178298736191.3843924.4213710231240809260.tip-bot2@tip-bot2?part=1
next prev parent reply other threads:[~2026-07-02 10:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 6:04 [PATCH 00/32] x86/msr: Drop 32-bit MSR interfaces Juergen Gross
2026-06-29 6:05 ` [PATCH 11/32] x86/pci: Stop using " Juergen Gross
2026-06-29 6:19 ` sashiko-bot
2026-07-02 10:16 ` [tip: x86/msr] " tip-bot2 for Juergen Gross
2026-07-02 10:25 ` sashiko-bot [this message]
2026-06-29 6:05 ` [PATCH 31/32] treewide: convert rdmsrq() from a macro to an inline function Juergen Gross
2026-06-29 6:24 ` sashiko-bot
2026-06-29 6:52 ` [PATCH 00/32] x86/msr: Drop 32-bit MSR interfaces Arnd Bergmann
2026-06-29 7:01 ` Jürgen Groß
2026-06-29 8:06 ` Arnd Bergmann
2026-06-29 8:15 ` Jürgen Groß
2026-06-29 8:38 ` Arnd Bergmann
2026-06-30 20:06 ` H. Peter Anvin
2026-06-29 11:19 ` Ingo Molnar
2026-06-30 18:59 ` Sean Christopherson
2026-07-01 8:33 ` Jürgen Groß
2026-07-02 10:07 ` Ingo Molnar
2026-07-02 11:03 ` Juergen Gross
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=20260702102527.2EF5C1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tip-bot2@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox