From: Arjan van de Ven <arjan@linux.intel.com>
To: Laurent Riffard <laurent.riffard@free.fr>
Cc: Kernel development list <linux-kernel@vger.kernel.org>, axboe@suse.de
Subject: Re: 2.6.17-rc6-mm1/pktcdvd - BUG: possible circular locking
Date: Mon, 12 Jun 2006 08:14:08 -0700 [thread overview]
Message-ID: <448D84C0.1070400@linux.intel.com> (raw)
In-Reply-To: <448875D1.5080905@free.fr>
Laurent Riffard wrote:
> Hello,
>
> This BUG happened while pktcdvd service was starting.
> Basically, the 2 following commands were issued:
> - modprobe ptkcdvd
> - pktsetup dvd /dev/dvd
This appears to be a real bug:
A normal pkt dvd block dev open takes the
bdev_mutex in the regular block device open path, which takes
ctl_mutex in the pkt_open function which gets called then from
the block layer.
HOWEVER the IOCTL path does it the other way around:
mutex_lock(&ctl_mutex);
ret = pkt_setup_dev(&ctrl_cmd);
mutex_unlock(&ctl_mutex);
where pkt_setup_dev in term calls pkt_new_dev which
calls blkdev_get(), which takes the bdev_mutex.
Looks very much like a AB-BA deadlock to me...
Jens?
next prev parent reply other threads:[~2006-06-12 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 19:09 2.6.17-rc6-mm1/pktcdvd - BUG: possible circular locking Laurent Riffard
2006-06-12 15:14 ` Arjan van de Ven [this message]
2006-06-12 16:41 ` Jens Axboe
2006-06-21 10:21 ` Arjan van de Ven
2006-06-22 14:50 ` Peter Osterlund
2006-06-22 18:20 ` Arjan van de Ven
2006-07-14 11:22 ` Peter Osterlund
2006-07-14 13:46 ` Arjan van de Ven
2006-07-14 21:06 ` Peter Osterlund
2006-07-14 22:29 ` Arjan van de Ven
2006-07-15 7:04 ` [patch] lockdep: annotate pktcdvd natural device hierarchy Arjan van de Ven
2006-07-15 10:35 ` Laurent Riffard
2006-07-15 10:57 ` Peter Osterlund
2006-07-16 10:33 ` Laurent Riffard
2006-07-25 2:27 ` Andrew Morton
2006-07-25 5:34 ` Arjan van de Ven
2006-07-25 6:31 ` Andrew Morton
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=448D84C0.1070400@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=axboe@suse.de \
--cc=laurent.riffard@free.fr \
--cc=linux-kernel@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