On 07.07.2006 08:33, Arjan van de Ven wrote: > hmm interesting; reiserfs seems to have another locking level layer for > the i_mutex due to the xattrs-are-a-directory thing. > > Can you try this patch below and see if that fixes it? The message is still there, but the details changed a bit: > Jul 7 19:15:48 gx110 kernel: [ 125.840979] > Jul 7 19:15:48 gx110 kernel: [ 125.840984] ============================================= > Jul 7 19:15:48 gx110 kernel: [ 125.841003] [ INFO: possible recursive locking detected ] > Jul 7 19:15:48 gx110 kernel: [ 125.841012] --------------------------------------------- > Jul 7 19:15:48 gx110 kernel: [ 125.841021] kdm/3242 is trying to acquire lock: > Jul 7 19:15:48 gx110 kernel: [ 125.841030] (&inode->i_mutex){--..}, at: [<c033c73a>] mutex_lock+0x1c/0x1f > Jul 7 19:15:48 gx110 kernel: [ 125.841077] > Jul 7 19:15:48 gx110 kernel: [ 125.841079] but task is already holding lock: > Jul 7 19:15:48 gx110 kernel: [ 125.841087] (&inode->i_mutex){--..}, at: [<c033c73a>] mutex_lock+0x1c/0x1f > Jul 7 19:15:48 gx110 kernel: [ 125.841105] > Jul 7 19:15:48 gx110 kernel: [ 125.841107] other info that might help us debug this: > Jul 7 19:15:48 gx110 kernel: [ 125.841117] 3 locks held by kdm/3242: > Jul 7 19:15:48 gx110 kernel: [ 125.841123] #0: (&inode->i_mutex){--..}, at: [<c033c73a>] mutex_lock+0x1c/0x1f > Jul 7 19:15:48 gx110 kernel: [ 125.841143] #1: (&REISERFS_I(inode)->xattr_sem){----}, at: [<c01bcb36>] reiserfs_acl_chmod+0xe0/0x182 > Jul 7 19:15:48 gx110 kernel: [ 125.841175] #2: (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<c01bcb6b>] reiserfs_acl_chmod+0x115/0x182 > Jul 7 19:15:48 gx110 kernel: [ 125.841197] > Jul 7 19:15:48 gx110 kernel: [ 125.841199] stack backtrace: > Jul 7 19:15:48 gx110 kernel: [ 125.841919] [<c0103f4d>] show_trace_log_lvl+0x54/0xfd > Jul 7 19:15:48 gx110 kernel: [ 125.841975] [<c010504d>] show_trace+0xd/0x10 > Jul 7 19:15:48 gx110 kernel: [ 125.842022] [<c0105067>] dump_stack+0x17/0x1c > Jul 7 19:15:48 gx110 kernel: [ 125.842067] [<c012e3fa>] __lock_acquire+0x758/0x9bf > Jul 7 19:15:48 gx110 kernel: [ 125.842314] [<c012e93e>] lock_acquire+0x5e/0x80 > Jul 7 19:15:48 gx110 kernel: [ 125.842550] [<c033c5b7>] __mutex_lock_slowpath+0xa7/0x20e > Jul 7 19:15:48 gx110 kernel: [ 125.842846] [<c033c73a>] mutex_lock+0x1c/0x1f > Jul 7 19:15:48 gx110 kernel: [ 125.843074] [<c01bbbb8>] reiserfs_xattr_set+0xe0/0x2bc > Jul 7 19:15:48 gx110 kernel: [ 125.844327] [<c01bc5d6>] reiserfs_set_acl+0x187/0x200 > Jul 7 19:15:48 gx110 kernel: [ 125.844957] [<c01bcb79>] reiserfs_acl_chmod+0x123/0x182 > Jul 7 19:15:48 gx110 kernel: [ 125.845581] [<c019ddab>] reiserfs_setattr+0x218/0x250 > Jul 7 19:15:48 gx110 kernel: [ 125.846168] [<c0174619>] notify_change+0x135/0x2c0 > Jul 7 19:15:48 gx110 kernel: [ 125.846637] [<c015b25a>] sys_fchmodat+0x9c/0xc3 > Jul 7 19:15:48 gx110 kernel: [ 125.847032] [<c015b293>] sys_chmod+0x12/0x14 > Jul 7 19:15:48 gx110 kernel: [ 125.847413] [<c0102cbd>] sysenter_past_esp+0x56/0x8d Thanks, Tilman -- Tilman Schmidt E-Mail: [email protected] Bonn, Germany
Attachment:
signature.asc
Description: OpenPGP digital signature
- References:
- Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected
- From: Tilman Schmidt <[email protected]>
- Re: Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected
- From: Arjan van de Ven <[email protected]>
- Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected
- Prev by Date: Re: 2.6.17-mm6
- Next by Date: Re: 2.6.17-mm6
- Previous by thread: Re: Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected
- Next by thread: Re: Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected
- Index(es):