From: Nishka Dasgupta <nishkadg.linux@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: of: Add of_node_put() before return in function
Date: Fri, 26 Jul 2019 13:02:52 +0530 [thread overview]
Message-ID: <af559a36-c926-e2a5-a401-aae0f6867a6e@gmail.com> (raw)
In-Reply-To: <20190724154701.GA4524@sirena.org.uk>
On 24/07/19 9:17 PM, Mark Brown wrote:
> On Wed, Jul 24, 2019 at 02:02:31PM +0530, Nishka Dasgupta wrote:
>> The local variable search in regulator_of_get_init_node takes the value
>> returned by either of_get_child_by_name or of_node_get, both of which
>> get a node. If this node is not put before returning, it could cause a
>> memory leak. Hence put search before a mid-loop return statement.
>> Issue found with Coccinelle.
>
>> - if (!strcmp(desc->of_match, name))
>> + if (!strcmp(desc->of_match, name)) {
>> + of_node_put(search);
>> return of_node_get(child);
>> + }
>
> Why not just remove the extra of_node_get() and a comment explaining why
> it's not needed?
>
I'm sorry, I don't think I understand. I'm putting search in this patch;
the program was already getting child. Should I also return child
directly instead of getting it again, and continue to put search?
Thanking you,
Nishka
next prev parent reply other threads:[~2019-07-26 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 8:32 Nishka Dasgupta
2019-07-24 15:47 ` Mark Brown
2019-07-26 7:32 ` Nishka Dasgupta [this message]
2019-07-26 10:45 ` Mark Brown
2019-07-31 13:11 ` Nishka Dasgupta
2019-07-31 19:08 ` Mark Brown
2019-08-01 13:10 ` Applied "regulator: of: Add of_node_put() before return in function" to the regulator tree Mark Brown
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=af559a36-c926-e2a5-a401-aae0f6867a6e@gmail.com \
--to=nishkadg.linux@gmail.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome