xfs-masters
[Top] [All Lists]

[xfs-masters] [Bug 7287] INFO: possible recursive locking detected: moun

To: xfs-masters@xxxxxxxxxxx
Subject: [xfs-masters] [Bug 7287] INFO: possible recursive locking detected: mount/3232 is trying to acquire lock
From: bugme-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 5 Apr 2007 06:41:45 -0700
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
http://bugzilla.kernel.org/show_bug.cgi?id=7287





------- Additional Comments From evil@xxxxxxxxxx  2007-04-05 06:41 -------
still there with 2.6.21-rc5, full dmesg & details here:
http://nerdbynature.de/bits/2.6.21-rc5/



[93422.248250] 
[93422.248254] =============================================
[93422.248268] [ INFO: possible recursive locking detected ]
[93422.248273] 2.6.21-rc5 #2
[93422.248276] ---------------------------------------------
[93422.248280] rm/32198 is trying to acquire lock:
[93422.248284]  (&(&ip->i_lock)->mr_lock){----}, at: [<c0246a31>]
xfs_ilock+0x71/0xa0
[93422.248299] 
[93422.248300] but task is already holding lock:
[93422.248304]  (&(&ip->i_lock)->mr_lock){----}, at: [<c0246a31>]
xfs_ilock+0x71/0xa0
[93422.248314] 
[93422.248314] other info that might help us debug this:
[93422.248320] 3 locks held by rm/32198:
[93422.248323]  #0:  (&inode->i_mutex/1){--..}, at: [<c0167026>]
do_unlinkat+0x96/0x160
[93422.248334]  #1:  (&inode->i_mutex){--..}, at: [<c0165305>] 
vfs_unlink+0x75/0xe0
[93422.248346]  #2:  (&(&ip->i_lock)->mr_lock){----}, at: [<c0246a31>]
xfs_ilock+0x71/0xa0
[93422.248356] 
[93422.248357] stack backtrace:
[93422.248362]  [<c0134b19>] __lock_acquire+0xa99/0x1010
[93422.248373]  [<c01350e7>] lock_acquire+0x57/0x70
[93422.248379]  [<c0246a31>] xfs_ilock+0x71/0xa0
[93422.248385]  [<c012e478>] down_write+0x38/0x50
[93422.248393]  [<c0246a31>] xfs_ilock+0x71/0xa0
[93422.248399]  [<c0246a31>] xfs_ilock+0x71/0xa0
[93422.248405]  [<c026bdb6>] xfs_lock_dir_and_entry+0xf6/0x100
[93422.248413]  [<c026c437>] xfs_remove+0x197/0x4e0
[93422.248419]  [<c016db79>] d_instantiate+0x19/0x40
[93422.248426]  [<c016d9e0>] d_rehash+0x20/0x50
[93422.248434]  [<c0165305>] vfs_unlink+0x75/0xe0
[93422.248442]  [<c0273e93>] xfs_vn_unlink+0x23/0x60
[93422.248449]  [<c03ccbaf>] __mutex_lock_slowpath+0x13f/0x280
[93422.248459]  [<c01339bb>] mark_held_locks+0x6b/0x90
[93422.248464]  [<c03ccbaf>] __mutex_lock_slowpath+0x13f/0x280
[93422.248471]  [<c03ccbaf>] __mutex_lock_slowpath+0x13f/0x280
[93422.248478]  [<c0133b49>] trace_hardirqs_on+0xb9/0x160
[93422.248484]  [<c0165305>] vfs_unlink+0x75/0xe0
[93422.248491]  [<c03ccba2>] __mutex_lock_slowpath+0x132/0x280
[93422.248498]  [<c0165305>] vfs_unlink+0x75/0xe0
[93422.248504]  [<c01648e1>] permission+0x91/0xf0
[93422.248512]  [<c0165319>] vfs_unlink+0x89/0xe0
[93422.248518]  [<c0167062>] do_unlinkat+0xd2/0x160
[93422.248526]  [<c0102894>] sysenter_past_esp+0x8d/0x99
[93422.248533]  [<c0133b49>] trace_hardirqs_on+0xb9/0x160
[93422.248541]  [<c0102864>] sysenter_past_esp+0x5d/0x99
[93422.248550]  =======================


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


<Prev in Thread] Current Thread [Next in Thread>
  • [xfs-masters] [Bug 7287] INFO: possible recursive locking detected: mount/3232 is trying to acquire lock, bugme-daemon <=