From: Tyrel Datwyler <turtle.in.the.kernel@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Laurent Vivier <lvivier@redhat.com>,
linux-kernel@vger.kernel.org
Cc: David Gibson <david@gibson.dropbear.id.au>,
linuxppc-dev@lists.ozlabs.org,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH] powerpc/pseries: Fix of_node_put() underflow during pseries remove
Date: Tue, 25 Jul 2017 10:53:23 -0700 [thread overview]
Message-ID: <f6209720-305b-0503-9549-d11f84b7ffbb@gmail.com> (raw)
In-Reply-To: <87inih6s23.fsf@concordia.ellerman.id.au>
On 07/24/2017 09:47 PM, Michael Ellerman wrote:
> Tyrel Datwyler <turtle.in.the.kernel@gmail.com> writes:
>
>> On 07/24/2017 03:42 AM, Michael Ellerman wrote:
>>> Laurent Vivier <lvivier@redhat.com> writes:
>>>
>>>> As for commit 68baf692c435 ("powerpc/pseries: Fix of_node_put()
>>>> underflow during DLPAR remove"), the call to of_node_put()
>>>> must be removed from pSeries_reconfig_remove_node().
>>>>
>>>> dlpar_detach_node() and pSeries_reconfig_remove_node() call
>>>> of_detach_node(), and thus the node should not be released
>>>> in this case too.
>>>>
>>>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>>>> ---
>>>> arch/powerpc/platforms/pseries/reconfig.c | 1 -
>>>> 1 file changed, 1 deletion(-)
>>>
>>> Thanks. I'll spare you the swearing about why we have the same bug in
>>> two places.
>>
>> That's probably my bad. I must have failed to test with older powerpc-util tooling where
>> drmgr uses the /proc/ofdt interface for device tree modification.
>
> OK. Really we should have automated tests of the various cases, I've
> just never had time to write any.
Agreed, some better CI is warranted.
>
> Mainly the thing that bugs me is that we still have the two separate
> paths. Or if we must maintain both they could at least share more code,
> the two functions do basically the same thing AFAICS.
Yeah, I think that is where I dropped the ball. I wrongly assumed by not looking close
enough that code was shared in those two paths. Definitely some code de-duplication work
that can be done.
-Tyrel
>
> cheers
>
next prev parent reply other threads:[~2017-07-25 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 14:51 Laurent Vivier
2017-07-24 0:56 ` David Gibson
2017-07-24 10:42 ` Michael Ellerman
2017-07-24 18:42 ` Tyrel Datwyler
2017-07-25 4:47 ` Michael Ellerman
2017-07-25 17:53 ` Tyrel Datwyler [this message]
2017-07-27 12:38 ` Michael Ellerman
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=f6209720-305b-0503-9549-d11f84b7ffbb@gmail.com \
--to=turtle.in.the.kernel@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvivier@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=thuth@redhat.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
all inboxes | Powered by JetHome®