Hide Forgot
Additional info: reporter: libreport-2.7.2 [ INFO: possible recursive locking detected ] 4.8.0-0.rc1.git3.1.fc26.x86_64 #1 Not tainted --------------------------------------------- kwriteconfig5/1219 is trying to acquire lock: (&ei->log_mutex){+.+...}, at: [<ffffffffc05c0e12>] btrfs_log_inode+0x162/0x10f0 [btrfs] but task is already holding lock: (&ei->log_mutex){+.+...}, at: [<ffffffffc05c0e12>] btrfs_log_inode+0x162/0x10f0 [btrfs] other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&ei->log_mutex); lock(&ei->log_mutex); *** DEADLOCK *** May be due to missing lock nesting notation 6 locks held by kwriteconfig5/1219: #0: (sb_writers#8){.+.+.+}, at: [<ffffffff892a6cf4>] __sb_start_write+0xb4/0xf0 #1: (&type->i_mutex_dir_key#3/1){+.+.+.}, at: [<ffffffff892af66a>] lock_rename+0xda/0x100 #2: (&sb->s_type->i_mutex_key#13){+.+.+.}, at: [<ffffffff892c3dde>] lock_two_nondirectories+0x3e/0x70 #3: (&sb->s_type->i_mutex_key#13/4){+.+...}, at: [<ffffffff892c3e06>] lock_two_nondirectories+0x66/0x70 #4: (sb_internal){.+.+.+}, at: [<ffffffff892a6cb8>] __sb_start_write+0x78/0xf0 #5: (&ei->log_mutex){+.+...}, at: [<ffffffffc05c0e12>] btrfs_log_inode+0x162/0x10f0 [btrfs] stack backtrace: CPU: 2 PID: 1219 Comm: kwriteconfig5 Not tainted 4.8.0-0.rc1.git3.1.fc26.x86_64 #1 Hardware name: System manufacturer System Product Name/P8Z77-V, BIOS 2104 08/13/2013 0000000000000086 000000009d76b8c0 ffff9ae739def7a0 ffffffff89467a83 ffffffff8ac03f70 ffff9ae739cc0000 ffff9ae739def868 ffffffff8910f22e 0000000039cc0df8 ffffffff00000006 00000000eb2a7c25 ffffffff8a503100 Call Trace: [<ffffffff89467a83>] dump_stack+0x86/0xc3 [<ffffffff8910f22e>] __lock_acquire+0x78e/0x1290 [<ffffffff89037f19>] ? sched_clock+0x9/0x10 [<ffffffff890ea6c7>] ? sched_clock_cpu+0xa7/0xc0 [<ffffffff898f658e>] ? mutex_unlock+0xe/0x10 [<ffffffff89110196>] lock_acquire+0xf6/0x1f0 [<ffffffffc05c0e12>] ? btrfs_log_inode+0x162/0x10f0 [btrfs] [<ffffffff898f5916>] mutex_lock_nested+0x86/0x3f0 [<ffffffffc05c0e12>] ? btrfs_log_inode+0x162/0x10f0 [btrfs] [<ffffffff898f658e>] ? mutex_unlock+0xe/0x10 [<ffffffffc05c0e12>] ? btrfs_log_inode+0x162/0x10f0 [btrfs] [<ffffffffc05c0e12>] btrfs_log_inode+0x162/0x10f0 [btrfs] [<ffffffff890deb69>] ? __might_sleep+0x49/0x80 [<ffffffffc05c193c>] btrfs_log_inode+0xc8c/0x10f0 [btrfs] [<ffffffff89037f19>] ? sched_clock+0x9/0x10 [<ffffffffc05c2070>] btrfs_log_inode_parent+0x240/0x940 [btrfs] [<ffffffff898f9257>] ? _raw_spin_unlock+0x27/0x40 [<ffffffffc057cdba>] ? btrfs_update_inode+0xda/0x110 [btrfs] [<ffffffffc05c3cf1>] btrfs_log_new_name+0x71/0x90 [btrfs] [<ffffffffc0586cd0>] btrfs_rename2+0x1090/0x17a0 [btrfs] [<ffffffff8912deed>] ? debug_lockdep_rcu_enabled+0x1d/0x20 [<ffffffff892c3e06>] ? lock_two_nondirectories+0x66/0x70 [<ffffffff892b12a2>] vfs_rename+0x5c2/0x970 [<ffffffff892af500>] ? __lookup_hash+0x10/0xa0 [<ffffffff892b7e27>] SyS_rename+0x3a7/0x3d0 [<ffffffff898f9bbc>] entry_SYSCALL_64_fastpath+0x1f/0xbd
Created attachment 1192239 [details] File: dmesg
The following all appear to be duplicates where the potential deadlock is reported at btrfs_log_inode+0x162 Bug 1366869 Bug 1368545 Bug 1369206 Bug 1373401 Bug 1385185 Bug 1402453 A possible fix was posted last week at https://patchwork.kernel.org/patch/9457035/
Doing some pruning, this bug looks to be years old. Please test on a newer kernel and reopen if the problem still exists.