Re: Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected

[Tilman Schmidt]

FYI, the issue is still present in 2.6.18-rc4 and 2.6.18-rc3-mm2.

Here's one output from 2.6.18-rc4:

> Aug 12 13:10:43 gx110 kernel: [   90.648896] ACPI: Getting cpuindex for acpiid 0x2
> Aug 12 13:10:45 gx110 kernel: [   91.809779]
> Aug 12 13:10:45 gx110 kernel: [   91.809784] =============================================
> Aug 12 13:10:45 gx110 kernel: [   91.809807] [ INFO: possible recursive locking detected ]
> Aug 12 13:10:45 gx110 kernel: [   91.809816] ---------------------------------------------
> Aug 12 13:10:45 gx110 kernel: [   91.809825] udevd/3770 is trying to acquire lock:
> Aug 12 13:10:45 gx110 kernel: [   91.809834]  (&inode->i_mutex){--..}, at: [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [   91.809884]
> Aug 12 13:10:45 gx110 kernel: [   91.809887] but task is already holding lock:
> Aug 12 13:10:45 gx110 kernel: [   91.809894]  (&inode->i_mutex){--..}, at: [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [   91.809912]
> Aug 12 13:10:45 gx110 kernel: [   91.809915] other info that might help us debug this:
> Aug 12 13:10:45 gx110 kernel: [   91.809924] 1 lock held by udevd/3770:
> Aug 12 13:10:45 gx110 kernel: [   91.809931]  #0:  (&inode->i_mutex){--..}, at: [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [   91.809951]
> Aug 12 13:10:45 gx110 kernel: [   91.809953] stack backtrace:
> Aug 12 13:10:45 gx110 kernel: [   91.810671]  [<c0103fa1>] show_trace_log_lvl+0x58/0x15b
> Aug 12 13:10:45 gx110 kernel: [   91.810729]  [<c01050ea>] show_trace+0xd/0x10
> Aug 12 13:10:45 gx110 kernel: [   91.810775]  [<c0105104>] dump_stack+0x17/0x1b
> Aug 12 13:10:45 gx110 kernel: [   91.810821]  [<c012d979>] __lock_acquire+0x74a/0x9a7
> Aug 12 13:10:45 gx110 kernel: [   91.811065]  [<c012de58>] lock_acquire+0x4a/0x6a
> Aug 12 13:10:45 gx110 kernel: [   91.811301]  [<c0338cc7>] __mutex_lock_slowpath+0xa7/0x20e
> Aug 12 13:10:45 gx110 kernel: [   91.811526]  [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [   91.811747]  [<c01b88f3>] xattr_readdir+0x50/0x44e
> Aug 12 13:10:45 gx110 kernel: [   91.812999]  [<c01b94aa>] reiserfs_chown_xattrs+0xda/0x10f
> Aug 12 13:10:45 gx110 kernel: [   91.813608]  [<c019c1ae>] reiserfs_setattr+0x106/0x243
> Aug 12 13:10:45 gx110 kernel: [   91.814185]  [<c0172f41>] notify_change+0x135/0x2bc
> Aug 12 13:10:45 gx110 kernel: [   91.814720]  [<c015a293>] chown_common+0x93/0xab
> Aug 12 13:10:45 gx110 kernel: [   91.815123]  [<c015a2de>] sys_chown+0x33/0x45
> Aug 12 13:10:45 gx110 kernel: [   91.815507]  [<c0102d0d>] sysenter_past_esp+0x56/0x8d
> Aug 12 13:10:45 gx110 kernel: [   91.815547] DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d
> Aug 12 13:10:45 gx110 kernel: [   91.815564] Leftover inexact backtrace:
> Aug 12 13:10:45 gx110 kernel: [   91.815578]  [<c01050ea>] show_trace+0xd/0x10
> Aug 12 13:10:45 gx110 kernel: [   91.815597]  [<c0105104>] dump_stack+0x17/0x1b
> Aug 12 13:10:45 gx110 kernel: [   91.815615]  [<c012d979>] __lock_acquire+0x74a/0x9a7
> Aug 12 13:10:45 gx110 kernel: [   91.815634]  [<c012de58>] lock_acquire+0x4a/0x6a
> Aug 12 13:10:45 gx110 kernel: [   91.815651]  [<c0338cc7>] __mutex_lock_slowpath+0xa7/0x20e
> Aug 12 13:10:45 gx110 kernel: [   91.815676]  [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [   91.815694]  [<c01b88f3>] xattr_readdir+0x50/0x44e
> Aug 12 13:10:45 gx110 kernel: [   91.815712]  [<c01b94aa>] reiserfs_chown_xattrs+0xda/0x10f
> Aug 12 13:10:45 gx110 kernel: [   91.815731]  [<c019c1ae>] reiserfs_setattr+0x106/0x243
> Aug 12 13:10:45 gx110 kernel: [   91.815750]  [<c0172f41>] notify_change+0x135/0x2bc
> Aug 12 13:10:45 gx110 kernel: [   91.815768]  [<c015a293>] chown_common+0x93/0xab
> Aug 12 13:10:45 gx110 kernel: [   91.815789]  [<c015a2de>] sys_chown+0x33/0x45
> Aug 12 13:10:45 gx110 kernel: [   91.815807]  [<c0102d0d>] sysenter_past_esp+0x56/0x8d
> Aug 12 13:10:47 gx110 kernel: [   94.483483] IA-32 Microcode Update Driver: v1.14a <tigran@xxxxxxxxxxx>

Thanks
Tilman

-- 
Tilman Schmidt                          E-Mail: tilman@xxxxxxx
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeoeffnet mindestens haltbar bis: (siehe Rueckseite)

Attachment: signature.asc
Description: OpenPGP digital signature