Linux Input/HID development
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Amitoj Kaur Chawla <amitoj1606@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: keyboard: cap11xx: Add missing of_node_put
Date: Thu, 28 Jan 2016 10:16:39 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.10.1601281014320.2516@hadrien> (raw)
In-Reply-To: <20160127234858.GI28687@dtor-ws>



On Wed, 27 Jan 2016, Dmitry Torokhov wrote:

> 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", &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.

Do you have a general strategy for this?

I asked Arnd Bergmann, and he said that if things were shared and if all
failures later in the function could use the shared label, then one should
use a label.  But I can see that there could be different opinions about
it.  Maybe two instances is not enough for sharing?  Maybe the fact that
the need for this error handling is limited to the loop means that there
should never be sharing?

thanks,
julia

>
> I believe there is another input driver that returns from
> for_each_child_of_node() without dropping reference.
>
> Thanks.
>
> --
> Dmitry
>

  reply	other threads:[~2016-01-28  9:17 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
2016-01-28  9:16   ` Julia Lawall [this message]
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=alpine.DEB.2.10.1601281014320.2516@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=amitoj1606@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --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