From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH 3/3] iommu/vt-d: Simplify domain_attach_iommu()
Date: Wed, 23 Apr 2025 11:10:20 +0800 [thread overview]
Message-ID: <20250423031020.2189546-4-baolu.lu@linux.intel.com> (raw)
In-Reply-To: <20250423031020.2189546-1-baolu.lu@linux.intel.com>
Use the __free(kfree) attribute with kzalloc() to automatically handle
the freeing of the allocated struct iommu_domain_info on error or early
exit paths, eliminating the need for explicit kfree() calls in error
handling branches.
Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
---
drivers/iommu/intel/iommu.c | 29 ++++++++---------------------
1 file changed, 8 insertions(+), 21 deletions(-)
diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
index 3a9ea0ad2cd3..12382c85495f 100644
--- a/drivers/iommu/intel/iommu.c
+++ b/drivers/iommu/intel/iommu.c
@@ -1337,13 +1337,14 @@ static bool first_level_by_default(struct intel_iommu *iommu)
int domain_attach_iommu(struct dmar_domain *domain, struct intel_iommu *iommu)
{
- struct iommu_domain_info *info, *curr;
- int num, ret = -ENOSPC;
+ struct iommu_domain_info *curr;
+ int num;
if (domain->domain.type == IOMMU_DOMAIN_SVA)
return 0;
- info = kzalloc(sizeof(*info), GFP_KERNEL);
+ struct iommu_domain_info *info __free(kfree) =
+ kzalloc(sizeof(*info), GFP_KERNEL);
if (!info)
return -ENOMEM;
@@ -1351,34 +1352,20 @@ int domain_attach_iommu(struct dmar_domain *domain, struct intel_iommu *iommu)
curr = xa_load(&domain->iommu_array, iommu->seq_id);
if (curr) {
curr->refcnt++;
- kfree(info);
return 0;
}
num = ida_alloc_range(&iommu->domain_ida, FLPT_DEFAULT_DID + 1,
cap_ndoms(iommu->cap) - 1, GFP_KERNEL);
- if (num < 0) {
- pr_err("%s: No free domain ids\n", iommu->name);
- goto err_unlock;
- }
+ if (num < 0)
+ return num;
info->refcnt = 1;
info->did = num;
info->iommu = iommu;
- curr = xa_cmpxchg(&domain->iommu_array, iommu->seq_id,
- NULL, info, GFP_KERNEL);
- if (curr) {
- ret = xa_err(curr) ? : -EBUSY;
- goto err_clear;
- }
- return 0;
-
-err_clear:
- ida_free(&iommu->domain_ida, info->did);
-err_unlock:
- kfree(info);
- return ret;
+ return xa_err(xa_store(&domain->iommu_array, iommu->seq_id,
+ no_free_ptr(info), GFP_KERNEL));
}
void domain_detach_iommu(struct dmar_domain *domain, struct intel_iommu *iommu)
--
2.43.0
next prev parent reply other threads:[~2025-04-23 3:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 3:10 [PATCH 0/3] iommu/vt-d: Use ida for domain ID management Lu Baolu
2025-04-23 3:10 ` [PATCH 1/3] iommu/vt-d: Use ida to manage domain id Lu Baolu
2025-04-24 7:37 ` Tian, Kevin
2025-04-24 9:01 ` Baolu Lu
2025-04-24 8:16 ` Baolu Lu
2025-04-23 3:10 ` [PATCH 2/3] iommu/vt-d: Replace spin_lock with mutex to protect domain ida Lu Baolu
2025-04-24 7:38 ` Tian, Kevin
2025-04-23 3:10 ` Lu Baolu [this message]
2025-04-24 7:46 ` [PATCH 3/3] iommu/vt-d: Simplify domain_attach_iommu() Tian, Kevin
2025-04-24 9:22 ` Baolu Lu
2025-04-24 13:37 ` Jason Gunthorpe
2025-04-24 14:47 ` Baolu Lu
2025-04-25 18:49 ` Dan Williams
2025-04-27 5:10 ` Baolu Lu
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=20250423031020.2189546-4-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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