Linux Power Management development
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Markus Elfring <Markus.Elfring@web.de>,
	linux-pm@vger.kernel.org, Lukasz Luba <lukasz.luba@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH] thermal/lib: Fix memory leak on error in thermal_genl_auto()
Date: Thu, 24 Oct 2024 14:57:09 +0200	[thread overview]
Message-ID: <9ba3fa17-57c3-41e9-9e19-33fa105a179e@linaro.org> (raw)
In-Reply-To: <45265aca-7371-455f-819f-c4d68cbb089b@web.de>

On 24/10/2024 14:02, Markus Elfring wrote:
>> The function thermal_genl_auto() does not free the allocated message
>> in the error path. Fix that by putting a out label and jump to it
>> which will free the message instead of directly returning an error.
> 
> Would you like to add any tags (like “Fixes” and “Cc”) accordingly?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc4#n145
> 
> 
> …
>> +++ b/tools/lib/thermal/commands.c
>> @@ -375,27 +375,30 @@ static thermal_error_t thermal_genl_auto(struct thermal_handler *th, cmd_cb_t cm
>>   					 struct cmd_param *param,
>>   					 int cmd, int flags, void *arg)
>>   {
>> +	thermal_error_t ret = THERMAL_ERROR;
>>   	struct nl_msg *msg;
>>   	void *hdr;
>>
>>   	msg = nlmsg_alloc();
>>   	if (!msg)
>> -		return THERMAL_ERROR;
>> +		goto out;
> …
> 
> Is it really reasonable to pass a null pointer (from a failed function call)
> to a subsequent nlmsg_free() call?

You are right, I should return here :S



> Can it be more appropriate to return directly in such an error case?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?h=v6.12-rc4#n532
> 
> Regards,
> Markus


-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2024-10-24 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 10:59 [PATCH] thermal/lib: Fix memory leak on error in thermal_genl_auto() Daniel Lezcano
2024-10-24 11:01 ` Daniel Lezcano
2024-10-24 11:07 ` Lukasz Luba
2024-10-24 12:02 ` Markus Elfring
2024-10-24 12:57   ` Daniel Lezcano [this message]
2024-10-24 13:18     ` Rafael J. Wysocki
2024-10-24 13:27       ` Lukasz Luba
2024-10-24 14:21       ` Daniel Lezcano
2024-10-24 15:19         ` Markus Elfring
2024-10-24 16:54           ` Daniel Lezcano

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=9ba3fa17-57c3-41e9-9e19-33fa105a179e@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=Markus.Elfring@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    /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