Most recent kernel where this bug did not occur: don't know Distribution: ubuntu 7.04 Hardware Environment: Desktop Motherboard: Asus A7V133-C, Processor: AMD Athlon XP 1600+, Software Environment: Problem Description: ============================================= [ INFO: possible recursive locking detected ] 2.6.23-rc8-mm2 #101 --------------------------------------------- beagled/3680 is trying to acquire lock: (&sb->s_type->i_mutex_key#6){--..}, at: [<c02bd867>] mutex_lock+0x1c/0x1f but task is already holding lock: (&sb->s_type->i_mutex_key#6){--..}, at: [<c02bd867>] mutex_lock+0x1c/0x1f other info that might help us debug this: 3 locks held by beagled/3680: #0: (&sb->s_type->i_mutex_key#6){--..}, at: [<c02bd867>] mutex_lock+0x1c/0x1f #1: (&REISERFS_I(inode)->xattr_sem){--..}, at: [<e18f41bc>] reiserfs_setxattr+0x4f/0xf6 [reiserfs] #2: (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<e18f41db>] reiserfs_setxattr+0x6e/0xf6 [reiserfs] stack backtrace: [<c0104f3f>] show_trace_log_lvl+0x1a/0x2f [<c01059c7>] show_trace+0x12/0x14 [<c0105ae6>] dump_stack+0x15/0x17 [<c0135b01>] __lock_acquire+0x171/0xb9b [<c01368ee>] lock_acquire+0x5d/0x75 [<c02bd6b5>] __mutex_lock_slowpath+0xdb/0x271 [<c02bd867>] mutex_lock+0x1c/0x1f [<e18f46c3>] reiserfs_xattr_set+0xd6/0x2b7 [reiserfs] [<e18f4990>] user_set+0x4c/0x57 [reiserfs] [<e18f41f3>] reiserfs_setxattr+0x86/0xf6 [reiserfs] [<c017837c>] vfs_setxattr+0x80/0xfd [<c01784b2>] setxattr+0xb9/0xd1 [<c0178573>] sys_lsetxattr+0x4c/0x66 [<c0103f0a>] sysenter_past_esp+0x5f/0x99 ======================= Steps to reproduce: - mount -t reiserfs -o noatime,nodiratime,user_xattr /dev/mapper/vglinux1-lvhome /home - log in the gnome desktop, this will launch beagled
Created attachment 13084 [details] Full dmesg
Created attachment 13085 [details] .config
This is surely fixed by now, isn't it?