From: Rob Herring <robherring2@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [PATCH] of: Fix locking when calling of_get_next_available_child()
Date: Mon, 11 Feb 2013 16:27:59 -0600 [thread overview]
Message-ID: <5119706F.1080902@gmail.com> (raw)
In-Reply-To: <1360621157-23570-1-git-send-email-grant.likely@secretlab.ca>
On 02/11/2013 04:19 PM, Grant Likely wrote:
> of_get_next_available_child() obtains the devtree_lock and then calls
> of_device_is_available() which also attempts to claim the lock. This is
> obviously incorrect and causes a deadlock on boot. Fix issue by adding
> an variant of of_device_is_available() which doesn't obtain the lock.
>
> Cc: Stephen Warren <swarren@wwwdotorg.org>
> Cc: Rob Herring <robherring2@gmail.com>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> ---
> drivers/of/base.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index e8d65af..4af74b7 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -297,7 +297,7 @@ EXPORT_SYMBOL(of_machine_is_compatible);
> * Returns 1 if the status property is absent or set to "okay" or "ok",
> * 0 otherwise
> */
> -int of_device_is_available(const struct device_node *device)
> +int __of_device_is_available(const struct device_node *device)
> {
> const char *status;
> int statlen;
> @@ -313,6 +313,17 @@ int of_device_is_available(const struct device_node *device)
>
> return 0;
> }
> +
> +int of_device_is_available(const struct device_node *device)
Stephen's version wins because he preserved the documentation. :)
Rob
> +{
> + unsigned long flags;
> + int rc;
> +
> + raw_spin_lock_irqsave(&devtree_lock, flags);
> + rc = __of_device_is_available(device);
> + raw_spin_unlock_irqrestore(&devtree_lock, flags);
> + return rc;
> +}
> EXPORT_SYMBOL(of_device_is_available);
>
> /**
> @@ -404,7 +415,7 @@ struct device_node *of_get_next_available_child(const struct device_node *node,
> raw_spin_lock(&devtree_lock);
> next = prev ? prev->sibling : node->child;
> for (; next; next = next->sibling) {
> - if (!of_device_is_available(next))
> + if (!__of_device_is_available(next))
> continue;
> if (of_node_get(next))
> break;
>
next prev parent reply other threads:[~2013-02-11 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 22:19 [PATCH] of: Fix locking when calling of_get_next_available_child() Grant Likely
2013-02-11 22:27 ` Rob Herring [this message]
2013-02-11 22:30 ` Grant Likely
2013-02-11 23:26 ` Stephen Warren
2013-02-12 15:20 ` Thierry Reding
2013-02-13 10:08 ` Grant Likely
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=5119706F.1080902@gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@wwwdotorg.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).