From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be>,
sboyd@kernel.org, dlan@gentoo.org
Cc: skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] clk: spacemit: fix resource leak in spacemit_ccu_reset_register
Date: Sat, 26 Jul 2025 11:16:02 +0200 [thread overview]
Message-ID: <ed5fcfec-6330-46e8-a302-5cf1d8b3a9ce@wanadoo.fr> (raw)
In-Reply-To: <20250723132504.66273-1-hendrik.hamerlinck@hammernet.be>
Le 23/07/2025 à 15:25, Hendrik Hamerlinck a écrit :
> The function spacemit_ccu_reset_register() allocates memory for an
> auxiliary device. If auxiliary_device_add() fails, it skips cleanup of
> these resources, resulting in leaks.
>
> Fix this by using the appropriate error handling path.
>
> Fixes: 988543522ebd ("clk: spacemit: set up reset auxiliary devices")
> Signed-off-by: Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be>
> Reviewed-by: Yixun Lan <dlan@gentoo.org>
> ---
> Changes in v2:
> - Properly place the Fixes tip.
> ---
> drivers/clk/spacemit/ccu-k1.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/spacemit/ccu-k1.c b/drivers/clk/spacemit/ccu-k1.c
> index 65e6de030717..5bb85e32c6cf 100644
> --- a/drivers/clk/spacemit/ccu-k1.c
> +++ b/drivers/clk/spacemit/ccu-k1.c
> @@ -1059,7 +1059,7 @@ static int spacemit_ccu_reset_register(struct device *dev,
> ret = auxiliary_device_add(adev);
> if (ret) {
> auxiliary_device_uninit(adev);
> - return ret;
> + goto err_free_aux_id;
> }
>
> return devm_add_action_or_reset(dev, spacemit_adev_unregister, adev);
Hi,
I'm not sure this is correct.
auxiliary_device_uninit() which is called if auxiliary_device_add()
fails should already do the clean-up.
So I would say that this patch adds a double-free issue and should not
be applied.
If I'm right, note that Stephen has already added a "Applied to clk-next"
CJ
next prev parent reply other threads:[~2025-07-26 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 13:25 [PATCH v2] clk: spacemit: fix resource leak in spacemit_ccu_reset_register Hendrik Hamerlinck
2025-07-25 2:36 ` Stephen Boyd
2025-07-26 9:16 ` Christophe JAILLET [this message]
2025-07-26 12:10 ` Yixun Lan
2025-07-26 12:57 ` Alex Elder
2025-07-26 18:00 ` Hendrik Hamerlinck
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=ed5fcfec-6330-46e8-a302-5cf1d8b3a9ce@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=dlan@gentoo.org \
--cc=hendrik.hamerlinck@hammernet.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=spacemit@lists.linux.dev \
/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