[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eb935f16-1f89-0be9-86c9-24e8a88c2d8b@linaro.org>
Date: Sat, 10 Jun 2023 18:23:58 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Andi Shyti <andi.shyti@...nel.org>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: Alim Akhtar <alim.akhtar@...sung.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>,
Thomas Abraham <thomas.abraham@...aro.org>,
Kukjin Kim <kgene.kim@...sung.com>,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [PATCH 1/2] tty: serial: samsung_tty: Fix a memory leak in
s3c24xx_serial_getclk() in case of error
On 10/06/2023 16:54, Andi Shyti wrote:
> On Sat, Jun 10, 2023 at 04:07:51PM +0200, Christophe JAILLET wrote:
>> Le 10/06/2023 à 12:26, Andi Shyti a écrit :
>>>> @@ -1459,8 +1459,10 @@ static unsigned int s3c24xx_serial_getclk(struct s3c24xx_uart_port *ourport,
>>>> continue;
>>>> rate = clk_get_rate(clk);
>>>> - if (!rate)
>>>> + if (!rate) {
>>>> + clk_put(clk);
>>>> continue;
>>>
>>> could you also print an error here?
>>>
>>
>> Is:
>> dev_err(ourport->port.dev,
>> "Failed to get clock rate for %s.\n", clkname);
Why do we need it? Most of other users of clk_get_rate() don't print.
Probably because such condition is highly unlikely if not impossible.
This makes simple function unnecessarily bigger...
Best regards,
Krzysztof
Powered by blists - more mailing lists