From: "Jason Dravet" <dravet@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: INFO: possible recursive locking detected
Date: Thu, 24 Aug 2006 12:58:29 -0500 [thread overview]
Message-ID: <BAY123-F83FB9BEE7F065A45CA6BDDF440@phx.gbl> (raw)
On a recent attempted install of fedora's rawhide I saw the following in my
anaconda.log file.
<4>=============================================
<4>[ INFO: possible recursive locking detected ]
<4>2.6.17-1.2571.fc6 #1
<4>---------------------------------------------
<4>anaconda/432 is trying to acquire lock:
<4> (&bdev->bd_mutex){--..}, at: [<c04658bb>] __blkdev_put+0x1f/0x11f
<4>
<4>but task is already holding lock:
<4> (&bdev->bd_mutex){--..}, at: [<c0465b4e>] do_open+0x6b/0x3b2
<4>
<4>other info that might help us debug this:
<4>1 lock held by anaconda/432:
<4> #0: (&bdev->bd_mutex){--..}, at: [<c0465b4e>] do_open+0x6b/0x3b2
<4>
<4>stack backtrace:
<4> [<c04037db>] show_trace_log_lvl+0x58/0x159
<4> [<c0403d9e>] show_trace+0xd/0x10
<4> [<c0403e3b>] dump_stack+0x19/0x1b
<4> [<c042bddb>] __lock_acquire+0x765/0x97c
<4> [<c042c563>] lock_acquire+0x4b/0x6c
<4> [<c05f37ee>] mutex_lock_nested+0xcb/0x214
<4> [<c04658bb>] __blkdev_put+0x1f/0x11f
<4> [<c04659d4>] blkdev_put+0xa/0xc
<4> [<c0465e26>] do_open+0x343/0x3b2
<4> [<c0466030>] blkdev_open+0x1f/0x48
<4> [<c045d83c>] __dentry_open+0xb8/0x186
<4> [<c045d978>] nameidata_to_filp+0x1c/0x2e
<4> [<c045d9b9>] do_filp_open+0x2f/0x36
<4> [<c045da00>] do_sys_open+0x40/0xbb
<4> [<c045daa7>] sys_open+0x16/0x18
<4> [<c0402e57>] syscall_call+0x7/0xb
<4>DWARF2 unwinder stuck at syscall_call+0x7/0xb
<4>Leftover inexact backtrace:
<4> [<c0403d9e>] show_trace+0xd/0x10
<4> [<c0403e3b>] dump_stack+0x19/0x1b
<4> [<c042bddb>] __lock_acquire+0x765/0x97c
<4> [<c042c563>] lock_acquire+0x4b/0x6c
<4> [<c05f37ee>] mutex_lock_nested+0xcb/0x214
<4> [<c04658bb>] __blkdev_put+0x1f/0x11f
<4> [<c04659d4>] blkdev_put+0xa/0xc
<4> [<c0465e26>] do_open+0x343/0x3b2
<4> [<c0466030>] blkdev_open+0x1f/0x48
<4> [<c045d83c>] __dentry_open+0xb8/0x186
<4> [<c045d978>] nameidata_to_filp+0x1c/0x2e
<4> [<c045d9b9>] do_filp_open+0x2f/0x36
<4> [<c045da00>] do_sys_open+0x40/0xbb
<4> [<c045daa7>] sys_open+0x16/0x18
<4> [<c0402e57>] syscall_call+0x7/0xb
Also posted at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203137
next reply other threads:[~2006-08-24 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 17:58 Jason Dravet [this message]
2011-06-23 6:54 Justin P. Mattock
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=BAY123-F83FB9BEE7F065A45CA6BDDF440@phx.gbl \
--to=dravet@hotmail.com \
--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
all inboxes | Powered by JetHome®