From: qhou <qi.hou@windriver.com>
To: Rob Herring <robh@kernel.org>
Cc: Peter Rosin <peda@axentia.se>, stable <stable@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Grant Likely <grant.likely@linaro.org>,
Bruce Ashfield <bruce.ashfield@windriver.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
ZhangXiao <xiao.zhang@windriver.com>
Subject: Re: [PATCH 1/3] of: fix of_node leak caused in of_find_node_opts_by_path
Date: Fri, 10 Feb 2017 09:15:21 +0800 [thread overview]
Message-ID: <d6b700db-7d94-eb93-3b89-3982b8670cd1@windriver.com> (raw)
In-Reply-To: <CAL_JsqJ210Nfwpi=pstTo+E8nTowVdLaMFNjd5rwSUpEcKcNJg@mail.gmail.com>
On 2017年02月09日 23:11, Rob Herring wrote:
> On Sun, Feb 5, 2017 at 10:55 PM, Qi Hou <qi.hou@windriver.com> wrote:
>> During stepping down the tree, parent node is gotten first and its refcount is
>> increased with of_node_get() in __of_get_next_child(). Since it just being used
>> as tmp node, its refcount must be decreased with of_node_put() after traversing
>> its child nodes.
>>
>> Or, its refcount will never be descreased to ZERO, then it will never be freed,
>> as well as other related memory blocks.
>>
>> To fix this, decrease refcount of parent with of_node_put() after
>> __of_find_node_by_path().
>>
>> Signed-off-by: Qi Hou <qi.hou@windriver.com>
>> Acked-by: Peter Rosin <peda@axentia.se>
>> ---
>> drivers/of/base.c | 3 +++
>> 1 file changed, 3 insertions(+)
> It doesn't look like there is any inter-dependency with this patch and
> the other 2, so I'll apply this one.
No, there is no inter-dependency in these three patches.
Just since they are all related with of_node_put and reported by
kmemleak and debugged
by the similar means, I sent them together.
-- Best regards,
Qi Hou
>
> Rob
prev parent reply other threads:[~2017-02-10 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 4:55 [PATCH 1/3] of: fix of_node leak caused in of_find_node_opts_by_path Qi Hou
2017-02-09 15:11 ` Rob Herring
2017-02-10 1:15 ` qhou [this message]
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=d6b700db-7d94-eb93-3b89-3982b8670cd1@windriver.com \
--to=qi.hou@windriver.com \
--cc=bruce.ashfield@windriver.com \
--cc=grant.likely@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=paul.gortmaker@windriver.com \
--cc=peda@axentia.se \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xiao.zhang@windriver.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