linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 2/2] clkdev: Fix race condition in clock lookup from device tree
Date: Mon, 19 Aug 2013 12:42:16 -0700	[thread overview]
Message-ID: <20130819194216.4443.2570@quantum> (raw)
In-Reply-To: <1376066046-16037-3-git-send-email-s.nawrocki@samsung.com>

Quoting Sylwester Nawrocki (2013-08-09 09:34:06)
> There is currently a race condition in the device tree part of clk_get()
> function, since the pointer returned from of_clk_get_by_name() may become
> invalid before __clk_get() call. For example, due to the clock provider
> driver remove() callback being called in between of_clk_get_by_name()
> and __clk_get().
> 
> Fix this by doing both the look up and __clk_get() operations with the
> clock providers list mutex held. This ensures that the clock pointer
> returned from __of_clk_get_from_provider() call and passed to __clk_get()
> is valid, as long as the clock supplier module first removes its clock
> provider instance and then does clk_unregister() on the corresponding
> clocks.
> 
> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>

Reviewed-by: Mike Turquette <mturquette@linaro.org>

I can take this through the clk tree if Russell's ACKs.

Regards,
Mike

> ---
>  drivers/clk/clkdev.c |   10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/clk/clkdev.c b/drivers/clk/clkdev.c
> index 442a313..4f5c4ef 100644
> --- a/drivers/clk/clkdev.c
> +++ b/drivers/clk/clkdev.c
> @@ -39,7 +39,13 @@ struct clk *of_clk_get(struct device_node *np, int index)
>         if (rc)
>                 return ERR_PTR(rc);
> 
> -       clk = of_clk_get_from_provider(&clkspec);
> +       of_clk_lock();
> +       clk = __of_clk_get_from_provider(&clkspec);
> +
> +       if (!IS_ERR(clk) && !__clk_get(clk))
> +               clk = ERR_PTR(-ENOENT);
> +
> +       of_clk_unlock();
>         of_node_put(clkspec.np);
>         return clk;
>  }
> @@ -157,7 +163,7 @@ struct clk *clk_get(struct device *dev, const char *con_id)
> 
>         if (dev) {
>                 clk = of_clk_get_by_name(dev->of_node, con_id);
> -               if (!IS_ERR(clk) && __clk_get(clk))
> +               if (!IS_ERR(clk))
>                         return clk;
>         }
> 
> --
> 1.7.9.5

      reply	other threads:[~2013-08-19 19:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 16:34 [PATCH RFC 0/2] clk: Fix potential race condition in clk_get() Sylwester Nawrocki
2013-08-09 16:34 ` [PATCH RFC 1/2] clk: Provide not locked variant of of_clk_get_from_provider() Sylwester Nawrocki
2013-08-19 19:41   ` Mike Turquette
2013-08-19 19:50     ` Russell King - ARM Linux
2013-08-20 17:31       ` Sylwester Nawrocki
2013-08-09 16:34 ` [PATCH RFC 2/2] clkdev: Fix race condition in clock lookup from device tree Sylwester Nawrocki
2013-08-19 19:42   ` Mike Turquette [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=20130819194216.4443.2570@quantum \
    --to=mturquette@linaro.org \
    --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).