Even if an IOMMU might be present for some PCI segment in the system,
that doesn't necessarily mean it provides translation for the device
we care about. Furthermore, the presence or not of one firmware flag
doesn't imply anything about the IOMMU driver's behaviour, which may
still depend on other firmware properties and kernel options too. What
actually matters is whether an IOMMU is enforcing protection for our
device - regardless of whether that stemmed from firmware policy, kernel
config, or user control - at the point we need to decide whether to
authorise it. We can ascertain that generically by simply looking at
whether we're currently attached to a translation domain or not.
Signed-off-by: Robin Murphy <robin.murphy@xxxxxxx>
---
I don't have the means to test this, but I'm at least 80% confident
in my unpicking of the structures to retrieve the correct device...
drivers/thunderbolt/domain.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/thunderbolt/domain.c b/drivers/thunderbolt/domain.c
index 7018d959f775..5f5fc5f6a09b 100644
--- a/drivers/thunderbolt/domain.c
+++ b/drivers/thunderbolt/domain.c
@@ -257,13 +257,14 @@ static ssize_t iommu_dma_protection_show(struct device *dev,
struct device_attribute *attr,
char *buf)
{
+ struct tb *tb = container_of(dev, struct tb, dev);
+ struct iommu_domain *iod = iommu_get_domain_for_dev(&tb->nhi->pdev->dev);
/*
* Kernel DMA protection is a feature where Thunderbolt security is
* handled natively using IOMMU. It is enabled when IOMMU is
- * enabled and ACPI DMAR table has DMAR_PLATFORM_OPT_IN set.
+ * enabled and actively enforcing translation.
*/
- return sprintf(buf, "%d\n",
- iommu_present(&pci_bus_type) && dmar_platform_optin());
+ return sprintf(buf, "%d\n", iod && iod->type != IOMMU_DOMAIN_IDENTITY);
}
static DEVICE_ATTR_RO(iommu_dma_protection);
--
2.28.0.dirty
