From: Grant Likely <grant.likely@linaro.org>
To: Nathan Fontenot <nfont@linux.vnet.ibm.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
stable <stable@vger.kernel.org>,
mdroth@linux.vnet.ibm.com
Subject: Re: [PATCH v2] powerpc/pseries: dynamically added OF nodes need to call of_node_init
Date: Tue, 15 Jul 2014 21:58:02 -0600 [thread overview]
Message-ID: <CACxGe6uGf3NKsxK9HPYRxPyKfVbR4GYkp5-zkRHN3GRuoqu3Nw@mail.gmail.com> (raw)
In-Reply-To: <53BEF099.5020705@linux.vnet.ibm.com>
On Thu, Jul 10, 2014 at 1:59 PM, Nathan Fontenot
<nfont@linux.vnet.ibm.com> wrote:
> On 07/10/2014 01:50 PM, Tyrel Datwyler wrote:
>> Commit 75b57ecf9 refactored device tree nodes to use kobjects such that they
>> can be exposed via /sysfs. A secondary commit 0829f6d1f furthered this rework
>> by moving the kobect initialization logic out of of_node_add into its own
>> of_node_init function. The inital commit removed the existing kref_init calls
>> in the pseries dlpar code with the assumption kobject initialization would
>> occur in of_node_add. The second commit had the side effect of triggering a
>> BUG_ON during DLPAR, migration and suspend/resume operations as a result of
>> dynamically added nodes being uninitialized.
>>
>> This patch fixes this by adding of_node_init calls in place of the previously
>> removed kref_init calls.
>>
>> Fixes: 0829f6d1f69e ("of: device_node kobject lifecycle fixes")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
>
> Acked-by: Nathan Fontenot <nfont@linux.vnet.ibm.com>
Acked-by: Grant Likely <grant.likely@linaro.org>
Ben, are you going to take this or should I take it via my tree?
g.
>
>> ---
>> V2:
>> - included stable kernel list on Cc per comment by mpe
>>
>> arch/powerpc/platforms/pseries/dlpar.c | 1 +
>> arch/powerpc/platforms/pseries/reconfig.c | 1 +
>> 2 files changed, 2 insertions(+)
>>
>> diff --git a/arch/powerpc/platforms/pseries/dlpar.c b/arch/powerpc/platforms/pseries/dlpar.c
>> index 022b38e..2d0b4d6 100644
>> --- a/arch/powerpc/platforms/pseries/dlpar.c
>> +++ b/arch/powerpc/platforms/pseries/dlpar.c
>> @@ -86,6 +86,7 @@ static struct device_node *dlpar_parse_cc_node(struct cc_workarea *ccwa,
>> }
>>
>> of_node_set_flag(dn, OF_DYNAMIC);
>> + of_node_init(dn);
>>
>> return dn;
>> }
>> diff --git a/arch/powerpc/platforms/pseries/reconfig.c b/arch/powerpc/platforms/pseries/reconfig.c
>> index 0435bb6..1c0a60d 100644
>> --- a/arch/powerpc/platforms/pseries/reconfig.c
>> +++ b/arch/powerpc/platforms/pseries/reconfig.c
>> @@ -69,6 +69,7 @@ static int pSeries_reconfig_add_node(const char *path, struct property *proplist
>>
>> np->properties = proplist;
>> of_node_set_flag(np, OF_DYNAMIC);
>> + of_node_init(np);
>>
>> np->parent = derive_parent(path);
>> if (IS_ERR(np->parent)) {
>>
>
prev parent reply other threads:[~2014-07-16 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 18:50 [PATCH v2] powerpc/pseries: dynamically added OF nodes need to call of_node_init Tyrel Datwyler
2014-07-10 19:59 ` Nathan Fontenot
2014-07-16 3:58 ` Grant Likely [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=CACxGe6uGf3NKsxK9HPYRxPyKfVbR4GYkp5-zkRHN3GRuoqu3Nw@mail.gmail.com \
--to=grant.likely@linaro.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--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).