public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-kernel@vger.kernel.org
Subject: [BUG?] possible recursive locking detected (blkdev_open)
Date: Wed, 9 Aug 2006 07:57:31 +0200	[thread overview]
Message-ID: <200608090757.32006.eike-kernel@sf-tec.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

=============================================
[ INFO: possible recursive locking detected ]
---------------------------------------------
parted/7929 is trying to acquire lock:
 (&bdev->bd_mutex){--..}, at: [<c105eb8d>] __blkdev_put+0x1e/0x13c

but task is already holding lock:
 (&bdev->bd_mutex){--..}, at: [<c105eec6>] do_open+0x72/0x3a8

other info that might help us debug this:
1 lock held by parted/7929:
 #0:  (&bdev->bd_mutex){--..}, at: [<c105eec6>] do_open+0x72/0x3a8
stack backtrace:
 [<c1003aad>] show_trace_log_lvl+0x58/0x15b
 [<c100495f>] show_trace+0xd/0x10
 [<c1004979>] dump_stack+0x17/0x1a
 [<c102dee5>] __lock_acquire+0x753/0x99c
 [<c102e3b0>] lock_acquire+0x4a/0x6a
 [<c1204501>] mutex_lock_nested+0xc8/0x20c
 [<c105eb8d>] __blkdev_put+0x1e/0x13c
 [<c105ecc4>] blkdev_put+0xa/0xc
 [<c105f18a>] do_open+0x336/0x3a8
 [<c105f21b>] blkdev_open+0x1f/0x4c
 [<c1057b40>] __dentry_open+0xc7/0x1aa
 [<c1057c91>] nameidata_to_filp+0x1c/0x2e
 [<c1057cd1>] do_filp_open+0x2e/0x35
 [<c1057dd7>] do_sys_open+0x38/0x68
 [<c1057e33>] sys_open+0x16/0x18
 [<c1002845>] sysenter_past_esp+0x56/0x8d
DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d
Leftover inexact backtrace:
 [<c100495f>] show_trace+0xd/0x10
 [<c1004979>] dump_stack+0x17/0x1a
 [<c102dee5>] __lock_acquire+0x753/0x99c
 [<c102e3b0>] lock_acquire+0x4a/0x6a
 [<c1204501>] mutex_lock_nested+0xc8/0x20c
 [<c105eb8d>] __blkdev_put+0x1e/0x13c
 [<c105ecc4>] blkdev_put+0xa/0xc
 [<c105f18a>] do_open+0x336/0x3a8
 [<c105f21b>] blkdev_open+0x1f/0x4c
 [<c1057b40>] __dentry_open+0xc7/0x1aa
 [<c1057c91>] nameidata_to_filp+0x1c/0x2e
 [<c1057cd1>] do_filp_open+0x2e/0x35
 [<c1057dd7>] do_sys_open+0x38/0x68
 [<c1057e33>] sys_open+0x16/0x18
 [<c1002845>] sysenter_past_esp+0x56/0x8d

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-08-09  5:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09  5:57 Rolf Eike Beer [this message]
2006-08-09  8:30 ` [BUG?] possible recursive locking detected (blkdev_open) Andrew Morton
2006-08-09  8:58   ` Rolf Eike Beer
2006-08-09 17:56   ` Dave Jones
2006-08-09 19:32     ` Andrew Morton
2006-08-18 10:35 ` Peter Zijlstra
2006-08-21  0:21   ` Neil Brown

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=200608090757.32006.eike-kernel@sf-tec.de \
    --to=eike-kernel@sf-tec.de \
    --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