======================================================= [ INFO: possible circular locking dependency detected ] 2.6.37-rc6+ #12 ------------------------------------------------------- grep/10562 is trying to acquire lock: (slub_lock){+++++.}, at: [] show_slab_objects+0xfc/0x390 but task is already holding lock: (s_active#182){++++.+}, at: [] sysfs_read_file+0x96/0x1c0 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (s_active#182){++++.+}: [] lock_acquire+0xa0/0x150 [] sysfs_deactivate+0x157/0x1c0 [] sysfs_addrm_finish+0x43/0x70 [] sysfs_remove_dir+0x7e/0xa0 [] kobject_del+0x16/0x40 [] kmem_cache_destroy+0x2f2/0x380 [] 0xffffffffa01b4bd1 [] sys_delete_module+0x1a2/0x280 [] system_call_fastpath+0x16/0x1b -> #0 (slub_lock){+++++.}: [] __lock_acquire+0x1370/0x1510 [] lock_acquire+0xa0/0x150 [] down_read+0x51/0xa0 [] show_slab_objects+0xfc/0x390 [] objects_show+0x13/0x20 [] slab_attr_show+0x22/0x30 [] sysfs_read_file+0xd9/0x1c0 [] vfs_read+0xcd/0x1a0 [] sys_read+0x54/0x90 [] system_call_fastpath+0x16/0x1b other info that might help us debug this: 2 locks held by grep/10562: #0: (&buffer->mutex){+.+.+.}, at: [] sysfs_read_file+0x46/0x1c0 #1: (s_active#182){++++.+}, at: [] sysfs_read_file+0x96/0x1c0 stack backtrace: Pid: 10562, comm: grep Tainted: G W 2.6.37-rc6+ #12 Call Trace: [] print_circular_bug+0xf9/0x100 [] __lock_acquire+0x1370/0x1510 [] ? sched_clock+0x9/0x10 [] ? check_object+0xac/0x250 [] lock_acquire+0xa0/0x150 [] ? show_slab_objects+0xfc/0x390 [] ? trace_hardirqs_on_caller+0x14d/0x190 [] down_read+0x51/0xa0 [] ? show_slab_objects+0xfc/0x390 [] show_slab_objects+0xfc/0x390 [] objects_show+0x13/0x20 [] slab_attr_show+0x22/0x30 [] sysfs_read_file+0xd9/0x1c0 [] vfs_read+0xcd/0x1a0 [] sys_read+0x54/0x90 [] system_call_fastpath+0x16/0x1b