From: Hans Petter Selasky <hselasky@c2i.net>
To: Antti Palosaari <crope@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: recursive locking problem
Date: Fri, 9 Sep 2011 09:51:51 +0200 [thread overview]
Message-ID: <201109090951.51252.hselasky@c2i.net> (raw)
In-Reply-To: <4E68EE98.90201@iki.fi>
On Thursday 08 September 2011 18:34:32 Antti Palosaari wrote:
> lock() + lock() + unlock() == free.
Hi,
As far as I can see the Linux kernel's mutex API doesn't have support for
checking if a mutex is owned. I guess you would have to do something like:
while (mutex_owned(&xxx))
mutex_unlock(&xxx);
--HPS
next prev parent reply other threads:[~2011-09-09 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 16:34 recursive locking problem Antti Palosaari
2011-09-09 7:51 ` Hans Petter Selasky [this message]
2011-09-09 10:45 ` David Waring
2011-09-13 20:59 ` Antti Palosaari
2011-09-13 21:34 ` Steve Kerrison
2011-09-13 21:58 ` Steven Toth
2011-09-13 22:10 ` Devin Heitmueller
2011-09-13 22:19 ` Steven Toth
2011-09-13 22:01 ` Devin Heitmueller
2011-09-09 11:46 ` Daniel Glöckner
2011-09-14 1:03 ` Antti Palosaari
2011-09-14 6:19 ` Daniel Glöckner
2011-09-14 10:45 ` Antti Palosaari
2011-09-14 12:22 ` Daniel Glöckner
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=201109090951.51252.hselasky@c2i.net \
--to=hselasky@c2i.net \
--cc=crope@iki.fi \
--cc=linux-media@vger.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