From: Brandon Philips <brandon@ifup.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media@vger.kernel.org, stable@kernel.org
Subject: [PATCH] ov511: fix probe() hang due to double mutex_lock
Date: Thu, 10 Dec 2009 17:04:49 -0800 [thread overview]
Message-ID: <20091211010449.GV3387@jenkins> (raw)
Commit 163fe744c3283fd267268629afff4cfc846ed0e0 added a double
mutex_lock which hangs ov51x_probe(). This was clearly a typo.
Change final mutex_lock() -> mutex_unlock()
Signed-off-by: Brandon Philips <bphilips@suse.de>
---
drivers/media/video/ov511.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/media/video/ov511.c b/drivers/media/video/ov511.c
index 0bc2cf5..2bed9e2 100644
--- a/drivers/media/video/ov511.c
+++ b/drivers/media/video/ov511.c
@@ -5878,7 +5878,7 @@ ov51x_probe(struct usb_interface *intf, const struct usb_device_id *id)
goto error;
}
- mutex_lock(&ov->lock);
+ mutex_unlock(&ov->lock);
return 0;
--
1.6.4.2
next reply other threads:[~2009-12-11 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 1:04 Brandon Philips [this message]
2009-12-11 3:32 ` [stable] [PATCH] ov511: fix probe() hang due to double mutex_lock Greg KH
2009-12-11 20:42 ` Brandon Philips
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=20091211010449.GV3387@jenkins \
--to=brandon@ifup.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=stable@kernel.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