From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>
Cc: 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 2/2] of: __of_detach_node() - remove node from phandle cache
Date: Fri, 14 Dec 2018 15:56:42 -0600 [thread overview]
Message-ID: <68a9e834-b11d-8b9f-1669-466709257f37@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAL_JsqJN69kbLX=Fn-hYh1FwWoU-S+sB7wHjG-9H5=ihbo3hcg@mail.gmail.com>
On 12/14/2018 11:20 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>
>>
>> Non-overlay dynamic devicetree node removal may leave the node in
>> the phandle cache. Subsequent calls to of_find_node_by_phandle()
>> will incorrectly find the stale entry. Remove the node from the
>> cache.
>>
>> Add paranoia checks in of_find_node_by_phandle() as a second level
>> of defense (do not return cached node if detached, do not add node
>> to cache if detached).
>>
>> Reported-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
>> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
>> ---
>> drivers/of/base.c | 29 ++++++++++++++++++++++++++++-
>> drivers/of/dynamic.c | 3 +++
>> drivers/of/of_private.h | 4 ++++
>> 3 files changed, 35 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/of/base.c b/drivers/of/base.c
>> index d599367cb92a..34a5125713c8 100644
>> --- a/drivers/of/base.c
>> +++ b/drivers/of/base.c
>> @@ -162,6 +162,27 @@ int of_free_phandle_cache(void)
>> late_initcall_sync(of_free_phandle_cache);
>> #endif
>>
>> +/*
>> + * Caller must hold devtree_lock.
>> + */
>> +void __of_free_phandle_cache_entry(phandle handle)
>> +{
>> + phandle masked_handle;
>> +
>> + if (!handle)
>> + return;
>> +
>> + masked_handle = handle & phandle_cache_mask;
>> +
>> + if (phandle_cache) {
>> + if (phandle_cache[masked_handle] &&
>> + handle == phandle_cache[masked_handle]->phandle) {
>> + of_node_put(phandle_cache[masked_handle]);
>> + phandle_cache[masked_handle] = NULL;
>> + }
>> + }
>> +}
>> +
>> void of_populate_phandle_cache(void)
>> {
>> unsigned long flags;
>> @@ -1209,11 +1230,17 @@ struct device_node *of_find_node_by_phandle(phandle handle)
>> if (phandle_cache[masked_handle] &&
>> handle == phandle_cache[masked_handle]->phandle)
>> np = phandle_cache[masked_handle];
>> + if (np && of_node_check_flag(np, OF_DETACHED)) {
>> + of_node_put(np);
>> + phandle_cache[masked_handle] = NULL;
>
> This should never happen, right? Any time we set OF_DETACHED, the
> entry should get removed from the cache. I think we want a WARN here
> in case we're in an unexpected state.
We don't actually remove the pointer from the phandle cache when we set
OF_DETACHED in drivers/of/dynamic.c:__of_detach_node. The phandle cache
is currently static within drivers/of/base.c. There are a couple of
calls to of_populate_phandle_cache / of_free_phandle_cache within
drivers/of/overlay.c, but these are not involved in the device tree
updates that occur during LPAR migration. A WARN here would only make
sense, if we also arrange to clear the handle.
>
> Rob
Michael
>
>
--
Michael W. Bringmann
Linux I/O, Networking and Security Development
IBM Corporation
Tie-Line 363-5196
External: (512) 286-5196
Cell: (512) 466-0650
mwb@linux.vnet.ibm.com
next prev parent reply other threads:[~2018-12-14 21:56 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
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 [this message]
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=68a9e834-b11d-8b9f-1669-466709257f37@linux.vnet.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=minkim@us.ibm.com \
--cc=mpe@ellerman.id.au \
--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).