xfs-masters
[Top] [All Lists]

[xfs-masters] [Bug 727] kernel 2.6.18.2: possible recursive locking dete

To: xfs-master@xxxxxxxxxxx
Subject: [xfs-masters] [Bug 727] kernel 2.6.18.2: possible recursive locking detected
From: bugzilla-daemon@xxxxxxxxxxx
Date: Sun, 7 Jan 2007 13:56:12 -0800
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=727


ejwtk06@xxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|kernel 2.6.18.2: possible   |kernel 2.6.18.2: possible
                   |recursive locking detected  |recursive locking detected




------- Additional Comments From ejwtk06@xxxxxxxxx  2007-01-07 13:56 CST -------
Potential recursive locking is still reported for latest stable kernel.

=============================================
[ INFO: possible recursive locking detected ]
2.6.19.1 #1
---------------------------------------------
dpkg/2607 is trying to acquire lock:
 (&(&ip->i_lock)->mr_lock){----}, at: [<ffffffff8032fb1a>] xfs_ilock+0x56/0x7a

but task is already holding lock:
 (&(&ip->i_lock)->mr_lock){----}, at: [<ffffffff8032fb1a>] xfs_ilock+0x56/0x7a

other info that might help us debug this:
3 locks held by dpkg/2607:
 #0:  (&inode->i_mutex/1){--..}, at: [<ffffffff80239fdc>] do_unlinkat+0x80/0x14
 #1:  (&inode->i_mutex){--..}, at: [<ffffffff8025fe23>] mutex_lock+0x23/0x27
 #2:  (&(&ip->i_lock)->mr_lock){----}, at: [<ffffffff8032fb1a>] xfs_ilock+0x56/

stack backtrace:

Call Trace:
 [<ffffffff802927c1>] __lock_acquire+0x37f/0xb0c
 [<ffffffff8032fb1a>] xfs_ilock+0x56/0x7a
 [<ffffffff8029343f>] lock_acquire+0x7c/0xa0
 [<ffffffff8032fb1a>] xfs_ilock+0x56/0x7a
 [<ffffffff8028f0e9>] down_write+0x33/0x3f
 [<ffffffff8032fb1a>] xfs_ilock+0x56/0x7a
 [<ffffffff8034ac13>] xfs_lock_dir_and_entry+0x8b/0xc6
 [<ffffffff8034ae58>] xfs_remove+0x20a/0x429
 [<ffffffff80292ef6>] __lock_acquire+0xab4/0xb0c
 [<ffffffff80354f21>] xfs_vn_unlink+0x26/0x60
 [<ffffffff8025fdcf>] __mutex_lock_slowpath+0x245/0x276
 [<ffffffff802379cd>] debug_mutex_free_waiter+0x50/0x55
 [<ffffffff8025fdf3>] __mutex_lock_slowpath+0x269/0x276
 [<ffffffff802479f7>] vfs_unlink+0xcd/0xfd
 [<ffffffff8023a027>] do_unlinkat+0xcb/0x144
 [<ffffffff80261212>] trace_hardirqs_on_thunk+0x35/0x37
 [<ffffffff80291f70>] trace_hardirqs_on+0xfd/0x127
 [<ffffffff80261212>] trace_hardirqs_on_thunk+0x35/0x37
 [<ffffffff802b84d0>] sys_unlink+0x11/0x13
 [<ffffffff8025b01e>] system_call+0x7e/0x83

-- 
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- 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 727] kernel 2.6.18.2: possible recursive locking detected, bugzilla-daemon <=