linux-kernel - INFO: possible recursive locking detected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <BAY123-F83FB9BEE7F065A45CA6BDDF440@phx.gbl>
Date:	Thu, 24 Aug 2006 12:58:29 -0500
From:	"Jason Dravet" <dravet@...mail.com>
To:	linux-kernel@...r.kernel.org
Subject: INFO: possible recursive locking detected

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/