From: Yi Liu <yi.l.liu@intel.com>
To: joro@8bytes.org, kevin.tian@intel.com, baolu.lu@linux.intel.com,
jgg@nvidia.com
Cc: yi.l.liu@intel.com, iommu@lists.linux.dev,
jacob.pan@linux.microsoft.com, robin.murphy@arm.com,
nicolinc@nvidia.com, will@kernel.org
Subject: [PATCH 2/2] iommu: Swap the order of setting group->pasid_array and __iommu_set_group_pasid()
Date: Sun, 19 Jan 2025 19:08:40 -0800 [thread overview]
Message-ID: <20250120030840.4171-3-yi.l.liu@intel.com> (raw)
In-Reply-To: <20250120030840.4171-1-yi.l.liu@intel.com>
Following the current order of setting group->pasid_array and
__iommu_set_group_pasid() in iommu_attach_device_pasid(), PRIs may be
forwarded to the domain before the attach succeeds. If the attach failed
in the end, the PRIs on the domain need to be flushed in the caller side.
Caller can do it, but it can be avoided by swapping the order. This is
more self-contained.
Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
Signed-off-by: Yi Liu <yi.l.liu@intel.com>
---
drivers/iommu/iommu.c | 23 ++++++++++++++++-------
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index 278c4eb8f225..b69bcf559839 100644
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@@ -3376,7 +3376,7 @@ int iommu_attach_device_pasid(struct iommu_domain *domain,
struct iommu_group *group = dev->iommu_group;
struct group_device *device;
const struct iommu_ops *ops;
- void *xa_entry;
+ void *curr, *xa_entry;
int ret;
if (!group)
@@ -3400,6 +3400,16 @@ int iommu_attach_device_pasid(struct iommu_domain *domain,
}
}
+ curr = xa_load(&group->pasid_array, pasid);
+ if (curr) {
+ ret = -EBUSY;
+ goto out_unlock;
+ }
+
+ ret = __iommu_set_group_pasid(domain, group, pasid);
+ if (ret)
+ goto out_unlock;
+
if (handle) {
handle->domain = domain;
xa_entry = xa_tag_pointer(handle, IOMMU_PASID_ARRAY_HANDLE);
@@ -3407,13 +3417,12 @@ int iommu_attach_device_pasid(struct iommu_domain *domain,
xa_entry = xa_tag_pointer(domain, IOMMU_PASID_ARRAY_DOMAIN);
}
- ret = xa_insert(&group->pasid_array, pasid, xa_entry, GFP_KERNEL);
- if (ret)
- goto out_unlock;
+ curr = xa_store(&group->pasid_array, pasid, handle, GFP_KERNEL);
+ if (curr) {
+ __iommu_remove_group_pasid(group, pasid, domain);
+ ret = xa_err(curr);
+ }
- ret = __iommu_set_group_pasid(domain, group, pasid);
- if (ret)
- xa_erase(&group->pasid_array, pasid);
out_unlock:
mutex_unlock(&group->mutex);
return ret;
--
2.34.1
next prev parent reply other threads:[~2025-01-20 3:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 3:08 [PATCH 0/2] Two enhancements to iommu_attach_device_pasid() Yi Liu
2025-01-20 3:08 ` [PATCH 1/2] iommu: Store either domain or handle in group->pasid_array Yi Liu
2025-01-20 5:55 ` Tian, Kevin
2025-01-20 15:55 ` Jason Gunthorpe
2025-01-21 2:02 ` Baolu Lu
2025-01-21 7:22 ` Yi Liu
2025-01-20 3:08 ` Yi Liu [this message]
2025-01-20 5:58 ` [PATCH 2/2] iommu: Swap the order of setting group->pasid_array and __iommu_set_group_pasid() Tian, Kevin
2025-01-20 6:57 ` Yi Liu
2025-01-20 16:13 ` Jason Gunthorpe
2025-01-21 9:27 ` Yi Liu
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=20250120030840.4171-3-yi.l.liu@intel.com \
--to=yi.l.liu@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.pan@linux.microsoft.com \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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