[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a9acf284-d55c-4c8e-9f34-c2feb26a446b@hammernet.be>
Date: Sat, 26 Jul 2025 20:00:10 +0200
From: Hendrik Hamerlinck <hendrik.hamerlinck@...mernet.be>
To: Alex Elder <elder@...e.org>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>, sboyd@...nel.org,
dlan@...too.org
Cc: skhan@...uxfoundation.org, linux-kernel-mentees@...ts.linux.dev,
linux-clk@...r.kernel.org, linux-riscv@...ts.infradead.org,
spacemit@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] clk: spacemit: fix resource leak in
spacemit_ccu_reset_register
On 7/26/25 14:57, Alex Elder wrote:
> On 7/26/25 4:16 AM, Christophe JAILLET wrote:
>> 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@...mernet.be>
>>> Reviewed-by: Yixun Lan <dlan@...too.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.
>
> I'm sure this patch is incorrect, and the original code did
> not have the stated problem. Thank you for calling attention
> to this Christophe.
>
> Stephen, could you please revert your commit of this patch?
>
> Thank you.
>
> -Alex
>
My apologies, I am terribly sorry for this mistake. I was convinced that
this was a leak but was not thorough enough in checking it.
Thank you for catching this issue in time. I will make sure to be more
careful in the future. Sorry for your troubles on this.
Kind regards,
Hendrik
Powered by blists - more mailing lists