Am 20.02.2007 22:23 schrieb Rafael J. Wysocki:
> Looks like reiserfs has some locking problems:
> 
> =============================================
> [ INFO: possible recursive locking detected ]
> 2.6.20-mm2 #6
> ---------------------------------------------
> beagled/4786 is trying to acquire lock:
>  (&inode->i_mutex){--..}, at: [<ffffffff80479df9>] mutex_lock+0x19/0x20
> 
> but task is already holding lock:
>  (&inode->i_mutex){--..}, at: [<ffffffff80479df9>] mutex_lock+0x19/0x20
> 
> other info that might help us debug this:
> 3 locks held by beagled/4786:
>  #0:  (&inode->i_mutex){--..}, at: [<ffffffff80479df9>] mutex_lock+0x19/0x20
>  #1:  (&REISERFS_I(inode)->xattr_sem){----}, at: [<ffffffff80304c99>] reiserfs_setxattr+0x79/0x150
>  #2:  (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<ffffffff80304cc0>] reiserfs_setxattr+0xa0/0x150

This looks like the same I have been seeing in every release
since 2.6.18. I reported it a couple of times, and Srinivasa Ds
tried a few fixes on me during 2.6.19-rc4, but we never got to
the bottom of it.

-- 
Tilman Schmidt                          E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)