[PATCH 3/4] iommufd: Require DMABUF revoke semantics

Leon Romanovsky posted 4 patches 4 weeks, 1 day ago
[PATCH 3/4] iommufd: Require DMABUF revoke semantics
Posted by Leon Romanovsky 4 weeks, 1 day ago
From: Leon Romanovsky <leonro@nvidia.com>

IOMMUFD does not support page fault handling, and after a call to
.move_notify() all mappings become invalid. Ensure that the IOMMUFD
DMABUF importer is bound to a revoke‑aware DMABUF exporter (for example,
VFIO).

Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
---
 drivers/iommu/iommufd/pages.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/iommu/iommufd/pages.c b/drivers/iommu/iommufd/pages.c
index dbe51ecb9a20..a233def71be0 100644
--- a/drivers/iommu/iommufd/pages.c
+++ b/drivers/iommu/iommufd/pages.c
@@ -1451,7 +1451,7 @@ static void iopt_revoke_notify(struct dma_buf_attachment *attach)
 
 static struct dma_buf_attach_ops iopt_dmabuf_attach_revoke_ops = {
 	.allow_peer2peer = true,
-	.move_notify = iopt_revoke_notify,
+	.revoke_notify = iopt_revoke_notify,
 };
 
 /*

-- 
2.52.0