From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] phy: rockchip-usb: add missing of_node_put
Date: Wed, 18 Nov 2015 11:31:29 -0800 [thread overview]
Message-ID: <20151118193129.GA48815@google.com> (raw)
In-Reply-To: <19587543.sZ81DoLUBT@diego>
On Wed, Nov 18, 2015 at 08:27:07PM +0100, Heiko St?bner wrote:
> Am Montag, 16. November 2015, 12:33:17 schrieb Julia Lawall:
> hmm, while I agree that the rockchip phy has an issue in the node lifecycle,
> I'm not sure that patch fixes it fully.
>
> It currently iterates over each phy, but would only of_node_put the phy it
> handled last. So if an error happens on the 3rd phy, the first 2 are already
> instantiated and would also get removed when the overall probe fails, but
> their of_node would never be "put".
Note the behavior of of_get_next_child() (and
of_get_next_available_child()); it "Decrements the refcount of prev." So
the loop only keeps a reference for (at most) one node at a time.
I believe Julia's patch is correct. It's possible the commit description
could have made this aspect clearer though, since I was confused about
this at first as well.
Regards,
Brian
next prev parent reply other threads:[~2015-11-18 19:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 11:33 [PATCH 0/7] add missing of_node_put Julia Lawall
2015-11-16 11:33 ` [PATCH 1/7] phy: brcmstb-sata: " Julia Lawall
2015-11-17 1:38 ` Brian Norris
2015-11-17 6:12 ` Julia Lawall
2015-11-17 17:44 ` Brian Norris
2015-11-17 17:48 ` Julia Lawall
2015-11-17 18:30 ` Brian Norris
2015-11-17 18:34 ` Brian Norris
2015-11-17 22:33 ` Julia Lawall
2015-11-18 19:05 ` device_node lifetime (was: Re: [PATCH 1/7] phy: brcmstb-sata: add missing of_node_put) Brian Norris
2015-11-18 20:39 ` Julia Lawall
2015-11-19 18:44 ` Rob Herring
2015-11-19 19:14 ` Russell King - ARM Linux
2015-11-27 14:14 ` [PATCH 1/7] phy: brcmstb-sata: add missing of_node_put Kishon Vijay Abraham I
2015-11-16 11:33 ` [PATCH 2/7] phy: mt65xx-usb3: " Julia Lawall
2015-11-16 11:33 ` [PATCH 4/7] phy: rockchip-usb: " Julia Lawall
2015-11-18 19:27 ` Heiko Stübner
2015-11-18 19:31 ` Brian Norris [this message]
2015-11-18 19:46 ` Heiko Stübner
2015-11-18 20:38 ` Julia Lawall
2015-11-18 20:40 ` Heiko Stübner
2015-11-18 21:42 ` Heiko Stübner
2015-11-16 11:33 ` [PATCH 5/7] phy: miphy28lp: " Julia Lawall
2015-11-16 11:33 ` [PATCH 6/7] phy: miphy365x: " Julia Lawall
2015-11-16 11:33 ` [PATCH 7/7] phy: cygnus: pcie: " Julia Lawall
2015-11-16 17:12 ` Ray Jui
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=20151118193129.GA48815@google.com \
--to=computersforpeace@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).