linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH] pinctrl: protect pinctrl_list add
Date: Mon, 03 Feb 2014 14:12:51 -0700	[thread overview]
Message-ID: <52F00653.40802@wwwdotorg.org> (raw)
In-Reply-To: <20140203113900.GD1725@redhat.com>

On 02/03/2014 04:39 AM, Stanislaw Gruszka wrote:
> We have few fedora bug reports about list corruption on pinctrl,
> for example:
> https://bugzilla.redhat.com/show_bug.cgi?id=1051918
> 
> Most likely corruption happen due lack of protection of pinctrl_list
> when adding new nodes to it. Patch corrects that.
> 
> Fixes: 57b676f9c1b ("pinctrl: fix and simplify locking")

After that patch ...

> diff --git a/drivers/pinctrl/core.c b/drivers/pinctrl/core.c

> @@ -851,7 +851,9 @@ static struct pinctrl *create_pinctrl(struct device *dev)
>  	kref_init(&p->users);
>  
>  	/* Add the pinctrl handle to the global list */
> +	mutex_lock(&pinctrl_list_mutex);

That variable doesn't exist; it got replaced with the "global"
pinctrl_mutex. Also, since that patch, IIRC some other changes have been
made to the locking structure, so this patch might need adjustments not
to conflict with those changes?

>  	list_add_tail(&p->node, &pinctrl_list);
> +	mutex_unlock(&pinctrl_list_mutex);


  reply	other threads:[~2014-02-03 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 11:39 [PATCH] pinctrl: protect pinctrl_list add Stanislaw Gruszka
2014-02-03 21:12 ` Stephen Warren [this message]
2014-02-04  8:01   ` Stanislaw Gruszka
2014-02-04  8:07     ` [PATCH v2] " Stanislaw Gruszka
2014-02-04 17:09       ` Stephen Warren
2014-02-04 21:08       ` Linus Walleij

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=52F00653.40802@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    --cc=swarren@nvidia.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).