From: Cyril Roelandt <tipecaml@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, michael@mihu.de,
mchehab@redhat.com, linux-media@vger.kernel.org,
Cyril Roelandt <tipecaml@gmail.com>
Subject: [PATCH 0/1] media: saa7146: don't use mutex_lock_interruptible in
Date: Tue, 11 Dec 2012 04:05:27 +0100 [thread overview]
Message-ID: <1355195128-10209-1-git-send-email-tipecaml@gmail.com> (raw)
This is the same kind of bug as the one fixed by
ddc43d6dc7df0849fe41b91460fa76145cf87b67 : mutex_lock() must be used in the
device_release file operation in order for all resources to be freed, since
returning -RESTARTSYS has no effect here.
I stole the commit log from Sylwester Nawrocki, who fixed a few of these issues,
since I could not formulate it better.
---
Cyril Roelandt (1):
media: saa7146: don't use mutex_lock_interruptible() in
device_release().
drivers/media/common/saa7146/saa7146_fops.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--
1.7.10.4
next reply other threads:[~2012-12-11 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 3:05 Cyril Roelandt [this message]
2012-12-11 3:05 ` [PATCH 1/1] media: saa7146: don't use mutex_lock_interruptible() in device_release() Cyril Roelandt
2012-12-11 7:22 ` Hans Verkuil
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=1355195128-10209-1-git-send-email-tipecaml@gmail.com \
--to=tipecaml@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=michael@mihu.de \
/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).