From: Dan Williams <dan.j.williams@intel.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
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: Re: [PATCH 3/3] iommu/vt-d: Simplify domain_attach_iommu()
Date: Fri, 25 Apr 2025 11:49:36 -0700 [thread overview]
Message-ID: <680bd94098249_1d522945b@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20250423031020.2189546-4-baolu.lu@linux.intel.com>
Lu Baolu wrote:
> 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)
[..]
> -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));
> }
This pattern looks like it wants a "xa_store_or_{reset,kfree}()" helper that
handles both canceling a scope based cleanup and taking responsibility for
error-exit-freeing @info in one statement.
I.e. this is similar to a:
"return devm_add_action_or_reset(..., no_free_ptr(obj), ...)"
...pattern.
next prev parent reply other threads:[~2025-04-25 18:49 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 ` [PATCH 3/3] iommu/vt-d: Simplify domain_attach_iommu() Lu Baolu
2025-04-24 7:46 ` 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 [this message]
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=680bd94098249_1d522945b@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=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
all inboxes | Powered by JetHome®