From: Mark Rutland <mark.rutland@arm.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Amitoj Kaur Chawla <amitoj1606@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
Devicetree List <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] of: resolver: Add missing of_node_put
Date: Thu, 28 Jan 2016 11:28:10 +0000 [thread overview]
Message-ID: <20160128112810.GK17123@leverpostej> (raw)
In-Reply-To: <alpine.DEB.2.02.1601272042030.2051@localhost6.localdomain6>
On Wed, Jan 27, 2016 at 08:48:00PM +0100, Julia Lawall wrote:
>
>
> On Wed, 27 Jan 2016, Pantelis Antoniou wrote:
>
> > Hi Mark,
> >
> > > On Jan 27, 2016, at 18:21 , Mark Rutland <mark.rutland@arm.com> wrote:
> > >
> > > On Wed, Jan 27, 2016 at 06:14:00PM +0200, Pantelis Antoniou wrote:
> > >> Hi Mark,
> > >>
> > >>> On Jan 27, 2016, at 18:05 , Mark Rutland <mark.rutland@arm.com> wrote:
> > >>>
> > >>> On Wed, Jan 27, 2016 at 08:50:17PM +0530, Amitoj Kaur Chawla wrote:
> > >>>> diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c
> > >>>> index 640eb4c..e2a0143 100644
> > >>>> --- a/drivers/of/resolver.c
> > >>>> +++ b/drivers/of/resolver.c
> > >>>> @@ -40,8 +40,10 @@ static struct device_node *__of_find_node_by_full_name(struct device_node *node,
> > >>>>
> > >>>> for_each_child_of_node(node, child) {
> > >>>> found = __of_find_node_by_full_name(child, full_name);
> > >>>> - if (found != NULL)
> > >>>> + if (found != NULL) {
> > >>>> + of_node_put(child);
> > >>>> return found;
> > >>>> + }
> > >>>> }
> > >>>>
> > >>>> return NULL;
> > >>>
> > >>> I don't think this is quite right. When child == found, this change will
> > >>> leave it decremented.
> > >>>
> > >>
> > >>
> > >> This patch is bogus.
> > >>
> > >> __of_find_node_by_full_name() is not taking a reference on the node if found.
> > >> This method relies on keeping the reference taken by the loop.
> > >
> > > Sure. For the found node, that makes sense.
> > >
> > > However, it also increments the refcount of all the parents, which does
> > > not seem correct to me, given they're not put on the return path, and a
> > > put of the found node won't decrement its parents refcounts, unless I
> > > have missed something.
> > >
> >
> > Hmm, yes. The parent refcounts must be decremented.
>
> So there should be if (found != child) of_node_put(child); ?
That would match the intended semantics, yes.
Thanks,
Mark.
next prev parent reply other threads:[~2016-01-28 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 15:20 [PATCH] of: resolver: Add missing of_node_put Amitoj Kaur Chawla
2016-01-27 16:05 ` Mark Rutland
2016-01-27 16:14 ` Pantelis Antoniou
[not found] ` <FE79FA58-A084-47BE-B872-7D57AC2B4D75-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2016-01-27 16:21 ` Mark Rutland
2016-01-27 18:02 ` Pantelis Antoniou
2016-01-27 19:48 ` Julia Lawall
2016-01-28 11:28 ` Mark Rutland [this message]
2016-01-28 11:36 ` Julia Lawall
[not found] ` <FF19B941-89E4-4954-9818-E352FE9A0E97-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2016-01-27 22:32 ` Julia Lawall
2016-01-29 16:45 ` Rob Herring
2016-01-29 17:33 ` Pantelis Antoniou
2016-01-29 23:46 ` Frank Rowand
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=20160128112810.GK17123@leverpostej \
--to=mark.rutland@arm.com \
--cc=amitoj1606@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@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