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>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5157576d0701082333h276b99f3l7a785f6e2f250c27@mail.gmail.com>
Date:	Tue, 9 Jan 2007 10:33:33 +0300
From:	"Tomasz Kvarsin" <kvarsin@...il.com>
To:	linux-kernel@...r.kernel.org, jfs-discussion@...ts.sourceforge.net,
	shaggy@...tin.ibm.com
Subject: JFS: possible recursive locking detected

This I got during boot with 2.6.20-rc4:
=============================================
[ INFO: possible recursive locking detected ]
2.6.20-rc4 #3
---------------------------------------------
mount/5819 is trying to acquire lock:
 (&jfs_ip->commit_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30

but task is already holding lock:
 (&jfs_ip->commit_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30

other info that might help us debug this:
2 locks held by mount/5819:
 #0:  (&inode->i_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30
 #1:  (&jfs_ip->commit_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30

stack backtrace:
 [<c010375a>] show_trace_log_lvl+0x1a/0x30
 [<c0103e62>] show_trace+0x12/0x20
 [<c0103f16>] dump_stack+0x16/0x20
 [<c0135e98>] __lock_acquire+0xa38/0xe00
 [<c01362cf>] lock_acquire+0x6f/0x90
 [<c033939a>] __mutex_lock_slowpath+0x6a/0x290
 [<c03395e1>] mutex_lock+0x21/0x30
 [<c01d64b0>] jfs_create+0x90/0x350
 [<c0169489>] vfs_create+0xa9/0xf0
 [<c016c5f7>] open_namei+0x5d7/0x630
 [<c01602fc>] do_filp_open+0x2c/0x60
 [<c0160377>] do_sys_open+0x47/0xe0
 [<c016044c>] sys_open+0x1c/0x20
 [<c0102f8e>] sysenter_past_esp+0x5f/0x99
 =======================
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ