[SRU][N:gke][PATCH 3/5] iommu: Skip PASID validation for devices without PASID capability
Tim Whisonant
tim.whisonant at canonical.com
Fri Oct 3 22:21:39 UTC 2025
From: Tushar Dave <tdave at nvidia.com>
BugLink: https://bugs.launchpad.net/bugs/2126453
Generally PASID support requires ACS settings that usually create
single device groups, but there are some niche cases where we can get
multi-device groups and still have working PASID support. The primary
issue is that PCI switches are not required to treat PASID tagged TLPs
specially so appropriate ACS settings are required to route all TLPs to
the host bridge if PASID is going to work properly.
pci_enable_pasid() does check that each device that will use PASID has
the proper ACS settings to achieve this routing.
However, no-PASID devices can be combined with PASID capable devices
within the same topology using non-uniform ACS settings. In this case
the no-PASID devices may not have strict route to host ACS flags and
end up being grouped with the PASID devices.
This configuration fails to allow use of the PASID within the iommu
core code which wrongly checks if the no-PASID device supports PASID.
Fix this by ignoring no-PASID devices during the PASID validation. They
will never issue a PASID TLP anyhow so they can be ignored.
Fixes: c404f55c26fc ("iommu: Validate the PASID in iommu_attach_device_pasid()")
Cc: stable at vger.kernel.org
Signed-off-by: Tushar Dave <tdave at nvidia.com>
Reviewed-by: Lu Baolu <baolu.lu at linux.intel.com>
Reviewed-by: Vasant Hegde <vasant.hegde at amd.com>
Link: https://lore.kernel.org/r/20250520011937.3230557-1-tdave@nvidia.com
Signed-off-by: Joerg Roedel <jroedel at suse.de>
(backported from commit b3f6fcd8404f9f92262303369bb877ec5d188a81)
[tswhison: adjusted context due to missing commits
8a9e1e773f60 ("iommu: Introduce a replace API for device pasid")
b45a3777ceab ("iommu: Pass old domain to set_dev_pasid op")
1fbf73425f51 ("iommu: Consolidate the ops->remove_dev_pasid usage into a helper")]
Signed-off-by: Tim Whisonant <tim.whisonant at canonical.com>
---
drivers/iommu/iommu.c | 22 ++++++++++++++++------
1 file changed, 16 insertions(+), 6 deletions(-)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index e606d250d1d55..d33faed9d899a 100644
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@@ -3514,9 +3514,11 @@ static int __iommu_set_group_pasid(struct iommu_domain *domain,
int ret;
for_each_group_device(group, device) {
- ret = domain->ops->set_dev_pasid(domain, device->dev, pasid);
- if (ret)
- goto err_revert;
+ if (device->dev->iommu->max_pasids > 0) {
+ ret = domain->ops->set_dev_pasid(domain, device->dev, pasid);
+ if (ret)
+ goto err_revert;
+ }
}
return 0;
@@ -3528,7 +3530,8 @@ static int __iommu_set_group_pasid(struct iommu_domain *domain,
if (device == last_gdev)
break;
- ops->remove_dev_pasid(device->dev, pasid);
+ if (device->dev->iommu->max_pasids > 0)
+ ops->remove_dev_pasid(device->dev, pasid);
}
return ret;
}
@@ -3541,7 +3544,8 @@ static void __iommu_remove_group_pasid(struct iommu_group *group,
for_each_group_device(group, device) {
ops = dev_iommu_ops(device->dev);
- ops->remove_dev_pasid(device->dev, pasid);
+ if (device->dev->iommu->max_pasids > 0)
+ ops->remove_dev_pasid(device->dev, pasid);
}
}
@@ -3574,7 +3578,13 @@ int iommu_attach_device_pasid(struct iommu_domain *domain,
mutex_lock(&group->mutex);
for_each_group_device(group, device) {
- if (pasid >= device->dev->iommu->max_pasids) {
+ /*
+ * Skip PASID validation for devices without PASID support
+ * (max_pasids = 0). These devices cannot issue transactions
+ * with PASID, so they don't affect group's PASID usage.
+ */
+ if ((device->dev->iommu->max_pasids > 0) &&
+ (pasid >= device->dev->iommu->max_pasids)) {
ret = -EINVAL;
goto out_unlock;
}
--
2.43.0
More information about the kernel-team
mailing list