From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Amitoj Kaur Chawla <amitoj1606@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
julia.lawall@lip6.fr
Subject: Re: [PATCH] input: keyboard: cap11xx: Add missing of_node_put
Date: Wed, 27 Jan 2016 15:48:58 -0800 [thread overview]
Message-ID: <20160127234858.GI28687@dtor-ws> (raw)
In-Reply-To: <20160125153121.GA21093@amitoj-Inspiron-3542>
On Mon, Jan 25, 2016 at 09:01:21PM +0530, Amitoj Kaur Chawla wrote:
> for_each_child_of_node performs an of_node_get on each iteration, so
> to break out of the loop an of_node_put is required.
>
> Found using Coccinelle. The semantic patch used for this is as follows:
>
> // <smpl>
> @@
> expression e;
> local idexpression n;
> @@
>
> for_each_child_of_node(..., n) {
> ... when != of_node_put(n)
> when != e = n
> (
> return n;
> |
> + of_node_put(n);
> ? return ...;
> )
> ...
> }
> // </smpl
>
> Signed-off-by: Amitoj Kaur Chawla <amitoj1606@gmail.com>
> ---
> drivers/input/keyboard/cap11xx.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/input/keyboard/cap11xx.c b/drivers/input/keyboard/cap11xx.c
> index 378db10..27cd7df 100644
> --- a/drivers/input/keyboard/cap11xx.c
> +++ b/drivers/input/keyboard/cap11xx.c
> @@ -304,8 +304,10 @@ static int cap11xx_init_leds(struct device *dev,
> led->cdev.brightness = LED_OFF;
>
> error = of_property_read_u32(child, "reg", ®);
> - if (error != 0 || reg >= num_leds)
> - return -EINVAL;
> + if (error != 0 || reg >= num_leds) {
> + error = -EINVAL;
> + goto putchild;
Instead of jumping to a label I added of_node_put here and also below
and applied, thank you.
I believe there is another input driver that returns from
for_each_child_of_node() without dropping reference.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2016-01-27 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:31 [PATCH] input: keyboard: cap11xx: Add missing of_node_put Amitoj Kaur Chawla
2016-01-27 23:48 ` Dmitry Torokhov [this message]
2016-01-28 9:16 ` Julia Lawall
2016-01-28 18:51 ` Dmitry Torokhov
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=20160127234858.GI28687@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=amitoj1606@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-input@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).