iommu: Standardize ATS robustness and state tracking
Subsystems (4)
v9 cover iommu: Standardize ATS robustness and state tracking
The primary motivation for this series is an ATS state mismatch observed under heavy load (via iova_stress). A failure in pci_enable_ats() leaves IOMMU drivers like arm-smmu-v3 with inconsistent state leading to PCI core warnings during device detach.
While David's recent work [1] addressed a discovery race for specific quirked devices by moving them to the HEADER phase, gaps remained regarding how Virtual Functions (VFs) inherit state from their Physical Functions (PFs). Specifically, pci_ats_supported() did not account for PF-level quirked status, and pci_prepare_ats() lacked STU validation for VFs.
Based on discussion with Jason and Baolu in v3/v5, it was decided that the IOMMU drivers should explicitly check pci_ats_supported() before calling pci_prepare_ats(). To enforce this, pci_prepare_ats() now noisily checks for support via WARN_ON(). Furthermore, the device probe should fail if pci_prepare_ats() fails. Since these early gates preclude software configuration errors, any remaining failure during pci_enable_ats() is treated as a kernel bug.
Following the discussion with the community, the driver-specific series have been posted separately:
- Intel IOMMU fixes reported by Sashiko [2]
- Refactors for AMD IOMMU [3]
[1] https://lore.kernel.org/linux-pci/[email protected]/
[2] https://lore.kernel.org/all/[email protected]/
[3] https://lore.kernel.org/all/[email protected]/
[v9]
- Collected R-b tags from Bjorn, Jason, Nicolin & Sami
- Folded in the dev_err into the WARN for arm-smmu-v3
[v8]
- https://lore.kernel.org/all/[email protected]/
- Collected R-b tags from Kevin & Lu
- Dropped the SMMU dev_iommu_priv_set(dev, NULL) patch.
[v7]
- https://lore.kernel.org/all/[email protected]/
- Moved patch PCI/ATS: Mandate checking pci_ats_supported() before pci_prepare_ats() to the AMD series [3] to maintain bisectibility
- Added a UAF fix for arm-smmu-v3 to set iommu->priv = NULL
[v6]
- Reverted the decoupling of pci_ats_supported() from pci_prepare_ats().
- Added a WARN_ON() to the internal support check in pci_prepare_ats().
- Dropped the standalone Intel bugfixes (RB-tree and UAF) to be sent as a separate standalone series per maintainer request.
- Kept the folded UAF fix in the AMD IOMMU patch to ensure the new error path is immediately safe.
- Collected Reviewed-by tags from Lu Baolu for PCI core patches.
[v5]
- https://lore.kernel.org/all/[email protected]/
- Decoupled pci_ats_supported() from pci_prepare_ats() in the PCI core.
- Rebased SMMUv3 support on top of Nicolin Chen's "Always-On ATS" series.
- Fixed pre-existing RB-tree corruption in VT-d probe (Baolu/Sashiko).
- Addressed the pre-existing UAF in AMD IOMMU probe suggested by Sashiko.
[v4]
- https://lore.kernel.org/all/[email protected]/
- Standardized the pattern across Intel VT-d and AMD IOMMU drivers.
- Replaced the SMMUv3 ats_prepared gate with a fatal probe-fail logic.
- Utilized WARN() macros for runtime enablement failures in all drivers.
- Collected R-b tags from Jason and Sami.
Pranjal Shrivastava (4):
PCI/ATS: Ensure pci_ats_supported() is PF-aware for VFs PCI/ATS: Validate STU for VFs in pci_prepare_ats() iommu/arm-smmu-v3: Standardize ATS enablement failure reporting iommu/vt-d: Fail probe on ATS configuration failure
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 9 +++++++-- drivers/iommu/intel/iommu.c | 15 ++++++++++++--- drivers/pci/ats.c | 13 ++++++++++--- 3 files changed, 29 insertions(+), 8 deletions(-)
base-commit: 6666bde33b83cb4fc9b1f7ba6a3471479f76ce72
Signature · 1 line
2.54.0.1136.gdb2ca164c4-goog
PATCH v9 1/4 PCI/ATS: Ensure pci_ats_supported() is PF-aware for VFs
Update pci_ats_supported() to additionally check the associated PF's status when called on a VF. This ensures that PF-level quirks and untrusted status are correctly propagated to VFs, providing a robust support check that aligns with the kernel's PF-centric ATS configuration model and is immune to the timing of VF-specific fixups.
--- drivers/pci/ats.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/pci/ats.c +5 -2
@@ -40,10 +40,13 @@ void pci_ats_init(struct pci_dev *dev)*/ bool pci_ats_supported (struct pci_dev *dev) { -if (!dev->ats_cap) +if (!dev->ats_cap || dev->untrusted)return false; -return (dev->untrusted ==0 ); +if (dev->is_virtfn) +return pci_ats_supported (pci_physfn (dev)); + +return true; }EXPORT_SYMBOL_GPL (pci_ats_supported);
Signature · 1 line
2.54.0.1136.gdb2ca164c4-goog
[email protected]
AI reviewRe: [PATCH v9 1/4] PCI/ATS: Ensure pci_ats_supported() is PF-aware for VFs
Sashiko has reviewed this patch and found no issues. It looks great!
Quoted 6 lines
Update
pci_ats_supported()to additionally check the associated PF's status when called on a VF. This ensures that PF-level quirks and untrusted status are correctly propagated to VFs, providing a robust support check that aligns with the kernel's PF-centric ATS configuration model and is immune to the timing of VF-specific fixups.
Quoted 7 lines
Reviewed-by Jason Gunthorpe <[email protected]>Reviewed-by Samiullah Khawaja <[email protected]>Reviewed-by Nicolin Chen <[email protected]>Reviewed-by Lu Baolu <[email protected]>Reviewed-by Kevin Tian <[email protected]>Acked-by Bjorn Helgaas <[email protected]>Signed-off-by Pranjal Shrivastava <[email protected]>
Sashiko has reviewed this patch and found no issues. It looks great!
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
PATCH v9 2/4 PCI/ATS: Validate STU for VFs in pci_prepare_ats()
In reply to Pranjal ShrivastavaWhile every PCI Function that implements ATS has an independent ATS Extended Capability structure with a Read/Write Smallest Translation Unit (STU) field, the kernel manages SR-IOV ATS by requiring the IOMMU driver to configure the STU on the Physical Function (PF) before any any Virtual Functions (VFs) are created.
Currently, pci_prepare_ats() bails out early for VFs, assuming that the PF has already been correctly prepared. However, this creates a potential mismatch if a VF is subsequently prepared with a different page shift.
Update pci_prepare_ats() to validate that the requested page shift (ps) matches the STU already configured in the associated PF. This ensures early detection of incompatible configurations and maintains the kernel's policy of consistent STU sizing across all functions associated with a given SMMU.
--- drivers/pci/ats.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/pci/ats.c +5 -1
@@ -73,8 +73,12 @@ int pci_prepare_ats(struct pci_dev *dev, int ps)if (ps <PCI_ATS_MIN_STU )return -EINVAL ; -if (dev->is_virtfn) +if (dev->is_virtfn) { +if (pci_physfn (dev)->ats_stu != ps) +return -EINVAL ; +return 0 ; + } dev->ats_stu = ps; ctrl =PCI_ATS_CTRL_STU (dev->ats_stu -PCI_ATS_MIN_STU );
Signature · 1 line
2.54.0.1136.gdb2ca164c4-goog
[email protected]
AI reviewRe: [PATCH v9 2/4] PCI/ATS: Validate STU for VFs in pci_prepare_ats()
Sashiko has reviewed this patch and found no issues. It looks great!
Quoted 16 lines
While every PCI Function that implements ATS has an independent ATS Extended Capability structure with a Read/Write Smallest Translation Unit (STU) field, the kernel manages SR-IOV ATS by requiring the IOMMU driver to configure the STU on the Physical Function (PF) before any any Virtual Functions (VFs) are created.
Currently,
pci_prepare_ats()bails out early for VFs, assuming that the PF has already been correctly prepared. However, this creates a potential mismatch if a VF is subsequently prepared with a different page shift.Update
pci_prepare_ats()to validate that the requested page shift (ps) matches the STU already configured in the associated PF. This ensures early detection of incompatible configurations and maintains the kernel's policy of consistent STU sizing across all functions associated with a given SMMU.
Quoted 7 lines
Reviewed-by Jason Gunthorpe <[email protected]>Reviewed-by Samiullah Khawaja <[email protected]>Reviewed-by Nicolin Chen <[email protected]>Reviewed-by Lu Baolu <[email protected]>Reviewed-by Kevin Tian <[email protected]>Acked-by Bjorn Helgaas <[email protected]>Signed-off-by Pranjal Shrivastava <[email protected]>
Sashiko has reviewed this patch and found no issues. It looks great!
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=2
PATCH v9 3/4 iommu/arm-smmu-v3: Standardize ATS enablement failure reporting
In reply to Pranjal ShrivastavaUpdate arm_smmu_enable_ats() to wrap the pci_enable_ats() call in a WARN(). Since probe-time checks now preclude configuration errors any failure during hardware enablement is considered a kernel bug.
--- drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c +7 -2
@@ -2956,8 +2956,13 @@ static void arm_smmu_enable_ats(struct arm_smmu_master *master)* ATC invalidation of PASID 0 causes the entire ATC to be flushed. */ arm_smmu_atc_inv_master (master,IOMMU_NO_PASID ); -if (pci_enable_ats (pdev, stu)) -dev_err (master->dev,"Failed to enable ATS (STU %zu)\n" , stu); + +/* +* Since pci_prepare_ats() has already verified the HW capability +* and programmed the STE, pci_enable_ats() should not fail here. +*/ +WARN (pci_enable_ats (pdev, stu), +"%s: Failed to enable ATS (STU %zu)\n" ,dev_name (master->dev), stu); }static int arm_smmu_enable_pasid (struct arm_smmu_master *master)
Signature · 1 line
2.54.0.1136.gdb2ca164c4-goog
[email protected]
AI reviewRe: [PATCH v9 3/4] iommu/arm-smmu-v3: Standardize ATS enablement failure reporting
Sashiko has reviewed this patch and found no issues. It looks great!
Quoted 9 lines
Update
arm_smmu_enable_ats()to wrap thepci_enable_ats()call in aWARN(). Since probe-time checks now preclude configuration errors any failure during hardware enablement is considered a kernel bug.Reviewed-by Kevin Tian <[email protected]>Reviewed-by Nicolin Chen <[email protected]>Reviewed-by Samiullah Khawaja <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Signed-off-by Pranjal Shrivastava <[email protected]>
Sashiko has reviewed this patch and found no issues. It looks great!
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=3
PATCH v9 4/4 iommu/vt-d: Fail probe on ATS configuration failure
In reply to Pranjal ShrivastavaUpdate the Intel VT-d driver to handle ATS configuration and enablement more strictly. Specifically, update the device probe to fail if pci_prepare_ats() returns an error. This ensures that any ATS-capable master reaching the attach phase is guaranteed to have a valid config.
Additionally, update iommu_enable_pci_ats() to WARN() if pci_enable_ats fails. Since earlier checks in the probe phase preclude config-related failures, any failure during hardware enablement is considered a kernel bug.
--- drivers/iommu/intel/iommu.c | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
drivers/iommu/intel/iommu.c +12 -3
@@ -876,8 +876,14 @@ static void iommu_enable_pci_ats(struct device_domain_info *info)if (!pci_ats_page_aligned (pdev))return ; -if (!pci_enable_ats (pdev,VTD_PAGE_SHIFT )) - info->ats_enabled =1 ; +/* +* pci_enable_ats() should not fail here because earlier checks +* have already verified support and configuration. +*/ +if (WARN_ON (pci_enable_ats (pdev,VTD_PAGE_SHIFT ))) +return ; + + info->ats_enabled =1 ; }static void iommu_disable_pci_ats (struct device_domain_info *info)
@@ -3292,7 +3298,10 @@ static struct iommu_device *intel_iommu_probe_device(struct device *dev)dev_iommu_priv_set (dev, info);if (pdev &&pci_ats_supported (pdev)) { -pci_prepare_ats (pdev,VTD_PAGE_SHIFT ); + ret =pci_prepare_ats (pdev,VTD_PAGE_SHIFT ); +if (ret) + goto free; + ret =device_rbtree_insert (iommu, info);if (ret) goto free;
Signature · 1 line
2.54.0.1136.gdb2ca164c4-goog
[email protected]
AI reviewRe: [PATCH v9 4/4] iommu/vt-d: Fail probe on ATS configuration failure
Sashiko has reviewed this patch and found no issues. It looks great!
Quoted 10 lines
Update the Intel VT-d driver to handle ATS configuration and enablement more strictly. Specifically, update the device probe to fail if
pci_prepare_ats()returns an error. This ensures that any ATS-capable master reaching the attach phase is guaranteed to have a valid config.Additionally, update
iommu_enable_pci_ats()toWARN()ifpci_enable_atsfails. Since earlier checks in the probe phase preclude config-related failures, any failure during hardware enablement is considered a kernel bug.
Quoted 5 lines
Reviewed-by Lu Baolu <[email protected]>Reviewed-by Kevin Tian <[email protected]>Reviewed-by Samiullah Khawaja <[email protected]>Reviewed-by Jason Gunthorpe <[email protected]>Signed-off-by Pranjal Shrivastava <[email protected]>
Sashiko has reviewed this patch and found no issues. It looks great!
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=4
Quoted 34 lines · Pranjal Shrivastava
The primary motivation for this series is an ATS state mismatch observed under heavy load (via
iova_stress). A failure inpci_enable_ats()leaves IOMMU drivers like arm-smmu-v3 with inconsistent state leading to PCI core warnings during device detach.While David's recent work [1] addressed a discovery race for specific quirked devices by moving them to the HEADER phase, gaps remained regarding how Virtual Functions (VFs) inherit state from their Physical Functions (PFs). Specifically,
pci_ats_supported()did not account for PF-level quirked status, andpci_prepare_ats()lacked STU validation for VFs.Based on discussion with Jason and Baolu in v3/v5, it was decided that the IOMMU drivers should explicitly check
pci_ats_supported()before callingpci_prepare_ats(). To enforce this,pci_prepare_ats()now noisily checks for support viaWARN_ON(). Furthermore, the device probe should fail ifpci_prepare_ats()fails. Since these early gates preclude software configuration errors, any remaining failure duringpci_enable_ats()is treated as a kernel bug.Following the discussion with the community, the driver-specific series have been posted separately:
- Intel IOMMU fixes reported by Sashiko [2]
- Refactors for AMD IOMMU [3][1] https://lore.kernel.org/linux-pci/[email protected]/
[2] https://lore.kernel.org/all/[email protected]/
[3] https://lore.kernel.org/all/[email protected]/[v9]
- Collected R-b tags from Bjorn, Jason, Nicolin & Sami
- Folded in thedev_errinto the WARN for arm-smmu-v3
[...]
Quoted 6 lines
Pranjal Shrivastava (4):
PCI/ATS: Ensurepci_ats_supported()is PF-aware for VFs PCI/ATS: Validate STU for VFs inpci_prepare_ats()iommu/arm-smmu-v3: Standardize ATS enablement failure reporting iommu/vt-d: Fail probe on ATS configuration failure
Quoted 7 lines
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 9 +++++++-- drivers/iommu/intel/iommu.c | 15 ++++++++++++--- drivers/pci/ats.c | 13 ++++++++++--- 3 files changed, 29 insertions(+), 8 deletions(-)base-commit:
6666bde33b83cb4fc9b1f7ba6a3471479f76ce72
Hi Joerg / Will,
Gentle ping on this, please LMK if anything else needs to be done for this seris?
Thanks,
Praan
Quoted 10 lines · Pranjal Shrivastava
Pranjal Shrivastava (4):
PCI/ATS: Ensurepci_ats_supported()is PF-aware for VFs PCI/ATS: Validate STU for VFs inpci_prepare_ats()iommu/arm-smmu-v3: Standardize ATS enablement failure reporting iommu/vt-d: Fail probe on ATS configuration failuredrivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 9 +++++++-- drivers/iommu/intel/iommu.c | 15 ++++++++++++--- drivers/pci/ats.c | 13 ++++++++++--- 3 files changed, 29 insertions(+), 8 deletions(-)
Applied, thanks.