From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: baolu.lu@linux.intel.com, "Tian, Kevin" <kevin.tian@intel.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] iommu/vt-d: Simplify domain_attach_iommu()
Date: Thu, 24 Apr 2025 22:47:52 +0800 [thread overview]
Message-ID: <013a07f4-140f-4cfe-9315-f3a77e081c8a@linux.intel.com> (raw)
In-Reply-To: <20250424133759.GA1213339@ziepe.ca>
On 4/24/2025 9:37 PM, Jason Gunthorpe wrote:
> On Thu, Apr 24, 2025 at 05:22:48PM +0800, Baolu Lu wrote:
>
>>>> -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));
>>>> }
>>> no_free_ptr() should be used before successful return. Here xa_store()
>>> could return error but at that point no auto free as no_free_ptr() already
>>> changes 'info' to NULL. then memory leak.
>> Hmm, I've considered this. My thought was that xa_store() failure only
>> occurs due to the system running out of memory, and the Linux kernel
>> can't recover from it. In that case, the system is already broken;
>> hence, handling the failure case here doesn't make things better.
> That's not the kernel pattern, you are supposed to unwind correctly in
> those failures
>
> I think you should not use cleanup.h for something complicated like
> this..
Okay, so let me drop this patch.
Thanks,
baolu
next prev parent reply other threads:[~2025-04-24 14:47 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 [this message]
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=013a07f4-140f-4cfe-9315-f3a77e081c8a@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