From: Vinod Koul <vkoul@kernel.org>
To: peter.ujfalusi@gmail.com, Haotian Zhang <vulab@iscas.ac.cn>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] omap-dma: fix dma_pool resource leak in error paths
Date: Tue, 23 Dec 2025 16:53:48 +0530 [thread overview]
Message-ID: <176648902866.689692.8514963839721463874.b4-ty@kernel.org> (raw)
In-Reply-To: <20251103073018.643-1-vulab@iscas.ac.cn>
On Mon, 03 Nov 2025 15:30:18 +0800, Haotian Zhang wrote:
> The dma_pool created by dma_pool_create() is not destroyed when
> dma_async_device_register() or of_dma_controller_register() fails,
> causing a resource leak in the probe error paths.
>
> Add dma_pool_destroy() in both error paths to properly release the
> allocated dma_pool resource.
>
> [...]
Applied, thanks!
[1/1] omap-dma: fix dma_pool resource leak in error paths
commit: 7b28c670df4508a7cb1ee31cb159b4366fcc6d4b
Best regards,
--
~Vinod
prev parent reply other threads:[~2025-12-23 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 7:30 Haotian Zhang
2025-12-23 11:23 ` Vinod Koul [this message]
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=176648902866.689692.8514963839721463874.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=vulab@iscas.ac.cn \
/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®