From: Rob Herring <robh@kernel.org>
To: frowand.list@gmail.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: refcount leak when phandle_cache entry replaced
Date: Wed, 11 Dec 2019 14:18:56 -0600 [thread overview]
Message-ID: <20191211201856.GA21857@bogus> (raw)
In-Reply-To: <1575965693-30395-1-git-send-email-frowand.list@gmail.com>
On Tue, 10 Dec 2019 02:14:53 -0600, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> of_find_node_by_phandle() does not do an of_node_put() of the existing
> node in a phandle cache entry when that node is replaced by a new node.
>
> Reported-by: Rob Herring <robh+dt@kernel.org>
> Fixes: b8a9ac1a5b99 ("of: of_node_get()/of_node_put() nodes held in phandle cache")
> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
> ---
>
> Checkpatch will warn about a line over 80 characters. Let me know
> if that bothers you.
>
> drivers/of/base.c | 2 ++
> 1 file changed, 2 insertions(+)
>
Applied, thanks.
Rob
next prev parent reply other threads:[~2019-12-11 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 8:14 [PATCH] of: refcount leak when phandle_cache entry replaced frowand.list
2019-12-11 20:18 ` Rob Herring [this message]
2019-12-12 11:17 ` Frank Rowand
2019-12-12 14:00 ` Rob Herring
2019-12-19 15:57 ` 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=20191211201856.GA21857@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@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;
as well as URLs for NNTP newsgroup(s).