From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: mwb@linux.vnet.ibm.com,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
tlfalcon@linux.vnet.ibm.com, minkim@us.ibm.com,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] of: of_node_get()/of_node_put() nodes held in phandle cache
Date: Fri, 14 Dec 2018 15:04:58 -0800 [thread overview]
Message-ID: <cb7caa9a-abcb-93c2-a3e9-185133f1241a@gmail.com> (raw)
In-Reply-To: <35cab334-0856-44e1-b18e-22668011b429@gmail.com>
On 12/14/18 2:47 PM, Frank Rowand wrote:
> On 12/14/18 9:15 AM, Rob Herring wrote:
>> On Fri, Dec 14, 2018 at 12:43 AM <frowand.list@gmail.com> wrote:
>>>
>>> From: Frank Rowand <frank.rowand@sony.com>
>>>
>>> The phandle cache contains struct device_node pointers. The refcount
>>> of the pointers was not incremented while in the cache, allowing use
>>> after free error after kfree() of the node. Add the proper increment
>>> and decrement of the use count.
>>
>> Since we pre-populate the cache at boot, all the nodes will have a ref
>> count and will never be freed unless we happen to repopulate the whole
>> cache. That doesn't seem ideal. The node pointer is not "in use" just
>> because it is in the cache.
I forgot to reply to this sentence.
The node pointers are "in use" because of_find_node_by_phandle() will
use the pointers to access the phandle field. This is a use after
free bug if the node has been kfree()'ed.
>>
>> Rob
>>
>
> This patch also adds of_node_put() so that the refcount will go to zero
> when the node is removed as part of an overlay remove, if the node was
> added by an overlay.
>
> Patch 2/2 adds the free cache entry call to __of_detach_node(), so the
> refcount will go to zero when the node is removed for dynamic use cases
> other than overlays. (For overlays, all nodes are instead removed from
> the cache before __of_detach_node() is called.)
>
> -Frank
>
next prev parent reply other threads:[~2018-12-14 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 6:42 [PATCH 0/2] of: phandle_cache, fix refcounts, remove stale entry frowand.list
2018-12-14 6:42 ` [PATCH 1/2] of: of_node_get()/of_node_put() nodes held in phandle cache frowand.list
2018-12-14 17:15 ` Rob Herring
2018-12-14 22:47 ` Frank Rowand
2018-12-14 23:04 ` Frank Rowand [this message]
2018-12-14 6:42 ` [PATCH 2/2] of: __of_detach_node() - remove node from " frowand.list
2018-12-14 17:20 ` Rob Herring
2018-12-14 21:56 ` Michael Bringmann
2018-12-14 22:38 ` Frank Rowand
2018-12-14 6:46 ` [PATCH 0/2] of: phandle_cache, fix refcounts, remove stale entry 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=cb7caa9a-abcb-93c2-a3e9-185133f1241a@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=minkim@us.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=mwb@linux.vnet.ibm.com \
--cc=robh+dt@kernel.org \
--cc=tlfalcon@linux.vnet.ibm.com \
--cc=tyreld@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).