From: Daniel Mack <zonque@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linus.walleij@linaro.org, patrice.chotard@st.com,
Daniel Mack <zonque@gmail.com>
Subject: [PATCH, for-next] pinctrl: fix mutex deadlock in get_pinctrl_dev_from_of_node()
Date: Fri, 26 Apr 2013 18:57:02 +0200 [thread overview]
Message-ID: <1366995422-7135-1-git-send-email-zonque@gmail.com> (raw)
This obvious bug was introduced by d755910b7 ("pinctrl: move subsystem
mutex to pinctrl_dev struct").
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
This applies on today's linux-next.
drivers/pinctrl/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/core.c b/drivers/pinctrl/core.c
index 37cd774..78eae4d 100644
--- a/drivers/pinctrl/core.c
+++ b/drivers/pinctrl/core.c
@@ -129,7 +129,7 @@ struct pinctrl_dev *get_pinctrl_dev_from_of_node(struct device_node *np)
return pctldev;
}
- mutex_lock(&pinctrldev_list_mutex);
+ mutex_unlock(&pinctrldev_list_mutex);
return NULL;
}
--
1.8.1.4
next reply other threads:[~2013-04-26 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 16:57 Daniel Mack [this message]
2013-04-29 12:47 ` [PATCH, for-next] pinctrl: fix mutex deadlock in get_pinctrl_dev_from_of_node() 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=1366995422-7135-1-git-send-email-zonque@gmail.com \
--to=zonque@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard@st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.