From: sashiko-bot@kernel.org
To: "Leon Romanovsky" <leon@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 06/13] PCI: Account for ACS egress control in isolation checks
Date: Thu, 06 Aug 2026 11:40:55 +0000 [thread overview]
Message-ID: <20260806114055.DB5951F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260806-fix-p2p-acs-v2-6-0cec14812965@nvidia.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Unchecked PCI configuration reads in Intel SPT PCH ACS quirks lead to hardware state corruption on read failures.
--
--- Patch [6]: [PATCH v2 06/13] PCI: Account for ACS egress control in isolation checks ---
commit 99c1da7ad98e7bc62ca4515768fee9a8109e4739
Author: Leon Romanovsky <leon@kernel.org>
PCI: Account for ACS egress control in isolation checks
This commit modifies ACS isolation checks to ensure peer requests cannot
bypass the IOMMU when Egress Control overrides Request Redirect. It also
updates the Intel SPT PCH quirk to gracefully handle configuration read
failures and properly enforce isolation rules.
[ ... ]
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index bb4c09cbbd10d..ebfe902b01182 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -4990,15 +4990,21 @@ static int pci_quirk_intel_spt_pch_acs(struct pci_dev *dev, u16 acs_flags)
> return -ENOTTY;
>
> /* see pci_acs_flags_enabled() */
> - pci_read_config_dword(dev, pos + PCI_ACS_CAP, &cap);
> + if (pci_read_config_dword(dev, pos + PCI_ACS_CAP, &cap))
> + return 0;
> acs_flags &= (cap | PCI_ACS_EC);
>
> - pci_read_config_dword(dev, pos + INTEL_SPT_ACS_CTRL, &ctrl);
> + if (pci_read_config_dword(dev, pos + INTEL_SPT_ACS_CTRL, &ctrl))
> + return 0;
[Severity: High]
This is a pre-existing issue, but since this patch adds return checks for
pci_read_config_dword() here, should similar checks be added to
pci_quirk_enable_intel_spt_pch_acs() and
pci_quirk_disable_intel_spt_pch_acs_redir() in the same file?
If pci_read_config_dword() fails in those functions, cap and ctrl are
populated with 0xFFFFFFFF by PCI_SET_ERROR_RESPONSE(). The subsequent
bitwise operations and write-back will write 0xFFFFFFFF (or 0xFFFFFFFF
masked in the disable function) to the INTEL_SPT_ACS_CTRL register,
setting all other writable bits.
For example, in pci_quirk_enable_intel_spt_pch_acs():
pci_read_config_dword(dev, pos + PCI_ACS_CAP, &cap);
pci_read_config_dword(dev, pos + INTEL_SPT_ACS_CTRL, &ctrl);
ctrl |= (cap & PCI_ACS_SV);
ctrl |= (cap & PCI_ACS_RR);
ctrl |= (cap & PCI_ACS_CR);
ctrl |= (cap & PCI_ACS_UF);
if (pci_ats_disabled() || dev->external_facing || dev->untrusted)
ctrl |= (cap & PCI_ACS_TB);
pci_write_config_dword(dev, pos + INTEL_SPT_ACS_CTRL, ctrl);
Could these unchecked reads lead to hardware state corruption on transient
read failures?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260806-fix-p2p-acs-v2-0-0cec14812965@nvidia.com?part=6
next prev parent reply other threads:[~2026-08-06 11:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 11:24 [PATCH v2 00/13] PCI/P2PDMA: Fix ACS egress control handling Leon Romanovsky
2026-08-06 11:24 ` [PATCH v2 01/13] PCI/P2PDMA: Safely terminate ACS redirect lists Leon Romanovsky
2026-08-06 11:32 ` sashiko-bot
2026-08-06 11:24 ` [PATCH v2 02/13] PCI/P2PDMA: Report ACS ports when the paths share no upstream bridge Leon Romanovsky
2026-08-06 11:37 ` sashiko-bot
2026-08-07 14:35 ` Leon Romanovsky
2026-08-06 11:24 ` [PATCH v2 03/13] PCI/P2PDMA: Document the Address Type assumption Leon Romanovsky
2026-08-06 11:28 ` sashiko-bot
2026-08-06 11:24 ` [PATCH v2 04/13] PCI: Account for Direct Translated P2P in ACS isolation checks Leon Romanovsky
2026-08-06 11:35 ` sashiko-bot
2026-08-06 11:24 ` [PATCH v2 05/13] PCI: Add ACS egress control vector accessor Leon Romanovsky
2026-08-06 11:39 ` sashiko-bot
2026-08-06 11:24 ` [PATCH v2 06/13] PCI: Account for ACS egress control in isolation checks Leon Romanovsky
2026-08-06 11:40 ` sashiko-bot [this message]
2026-08-07 16:07 ` Leon Romanovsky
2026-08-06 11:24 ` [PATCH v2 07/13] PCI/P2PDMA: Derive peer-to-peer routing from ACS control bits Leon Romanovsky
2026-08-06 11:33 ` sashiko-bot
2026-08-06 11:24 ` [PATCH v2 08/13] PCI/P2PDMA: Honor ACS egress control vectors Leon Romanovsky
2026-08-06 11:47 ` sashiko-bot
2026-08-06 11:24 ` [PATCH v2 09/13] PCI/P2PDMA: Document ACS egress control handling Leon Romanovsky
2026-08-06 11:29 ` sashiko-bot
2026-08-06 11:24 ` [PATCH v2 10/13] PCI/P2PDMA: Extract pure ACS routing decision helpers Leon Romanovsky
2026-08-06 11:34 ` sashiko-bot
2026-08-06 11:24 ` [PATCH v2 11/13] PCI/P2PDMA: Add KUnit tests for ACS routing decisions Leon Romanovsky
2026-08-06 11:34 ` sashiko-bot
2026-08-06 11:24 ` [PATCH v2 12/13] PCI/P2PDMA: Add KUnit coverage for the ACS P2P routing walk Leon Romanovsky
2026-08-06 11:44 ` sashiko-bot
2026-08-07 13:02 ` Leon Romanovsky
2026-08-06 11:24 ` [PATCH v2 13/13] PCI: Add KUnit coverage for ACS isolation checks Leon Romanovsky
2026-08-06 11:37 ` sashiko-bot
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=20260806114055.DB5951F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=leon@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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