Bug 1369206

Summary: [abrt] [ INFO: possible recursive locking detected ]
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: bugzilla, gansalmon, ichavero, itamar, jonathan, kernel-maint, lars.s.jensen, madhu.chinakonda, mchehab, mschmidt, redhat, xzj8b3
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fc3f40347561891808f07927752a6f5ddebf23fc
Whiteboard: abrt_hash:15f09be2ede24406284ff71bafababcbd1525870;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-23 23:03:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description Chris Murphy 2016-08-22 16:20:52 UTC
Description of problem:
I get a notification of a problem in gnome-shell shortly after logging in, so I'm not really sure what caused it.

Additional info:
reporter:       libreport-2.7.2
[ INFO: possible recursive locking detected ]
4.8.0-0.rc2.git3.1.fc25.x86_64 #1 Not tainted
---------------------------------------------
cupsd/1438 is trying to acquire lock:
 (&ei->log_mutex){+.+...}, at: [<ffffffffc029ae12>] btrfs_log_inode+0x162/0x10f0 [btrfs]

but task is already holding lock:
 (&ei->log_mutex){+.+...}, at: [<ffffffffc029ae12>] 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

5 locks held by cupsd/1438:
 #0:  (sb_writers#8){.+.+.+}, at: [<ffffffff9e2a70b4>] __sb_start_write+0xb4/0xf0
 #1:  (&type->i_mutex_dir_key#3/1){+.+.+.}, at: [<ffffffff9e2afa2a>] lock_rename+0xda/0x100
 #2:  (&sb->s_type->i_mutex_key#13/4){+.+...}, at: [<ffffffff9e2c41c6>] lock_two_nondirectories+0x66/0x70
 #3:  (sb_internal){.+.+.+}, at: [<ffffffff9e2a7078>] __sb_start_write+0x78/0xf0
 #4:  (&ei->log_mutex){+.+...}, at: [<ffffffffc029ae12>] btrfs_log_inode+0x162/0x10f0 [btrfs]

stack backtrace:
CPU: 1 PID: 1438 Comm: cupsd Not tainted 4.8.0-0.rc2.git3.1.fc25.x86_64 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.1-1.fc24 04/01/2014
 0000000000000086 00000000cda3dbda ffff9e9cc2b037a0 ffffffff9e467eb3
 ffffffff9fbe0ba0 ffff9e9cc2af8000 ffff9e9cc2b03868 ffffffff9e10f27e
 00000000c2b037d0 ffffffff00000005 000000009e8f661e ffffffff9f4e0e00
Call Trace:
 [<ffffffff9e467eb3>] dump_stack+0x86/0xc3
 [<ffffffff9e10f27e>] __lock_acquire+0x78e/0x1290
 [<ffffffff9e037f29>] ? sched_clock+0x9/0x10
 [<ffffffff9e0ea687>] ? sched_clock_cpu+0xa7/0xc0
 [<ffffffff9e8f661e>] ? mutex_unlock+0xe/0x10
 [<ffffffff9e1101e6>] lock_acquire+0xf6/0x1f0
 [<ffffffffc029ae12>] ? btrfs_log_inode+0x162/0x10f0 [btrfs]
 [<ffffffff9e8f59a6>] mutex_lock_nested+0x86/0x3f0
 [<ffffffffc029ae12>] ? btrfs_log_inode+0x162/0x10f0 [btrfs]
 [<ffffffff9e8f661e>] ? mutex_unlock+0xe/0x10
 [<ffffffffc029ae12>] ? btrfs_log_inode+0x162/0x10f0 [btrfs]
 [<ffffffffc029ae12>] btrfs_log_inode+0x162/0x10f0 [btrfs]
 [<ffffffff9e0deb69>] ? __might_sleep+0x49/0x80
 [<ffffffffc029b93c>] btrfs_log_inode+0xc8c/0x10f0 [btrfs]
 [<ffffffff9e037f29>] ? sched_clock+0x9/0x10
 [<ffffffff9e8f661e>] ? mutex_unlock+0xe/0x10
 [<ffffffffc029c070>] btrfs_log_inode_parent+0x240/0x940 [btrfs]
 [<ffffffff9e8f92e7>] ? _raw_spin_unlock+0x27/0x40
 [<ffffffffc0256dba>] ? btrfs_update_inode+0xda/0x110 [btrfs]
 [<ffffffffc029dcf1>] btrfs_log_new_name+0x71/0x90 [btrfs]
 [<ffffffffc0260cd0>] btrfs_rename2+0x1090/0x17a0 [btrfs]
 [<ffffffff9e12df4d>] ? debug_lockdep_rcu_enabled+0x1d/0x20
 [<ffffffff9e2c41c6>] ? lock_two_nondirectories+0x66/0x70
 [<ffffffff9e2b1662>] vfs_rename+0x5c2/0x970
 [<ffffffff9e2af900>] ? __lookup_hash+0x50/0xa0
 [<ffffffff9e2b81e7>] SyS_rename+0x3a7/0x3d0
 [<ffffffff9e8f9c3c>] entry_SYSCALL_64_fastpath+0x1f/0xbd

Potential duplicate: bug 1368545

Comment 1 Chris Murphy 2016-08-22 16:21:00 UTC
Created attachment 1193007 [details]
File: dmesg

Comment 2 Chris Murphy 2016-08-22 16:46:08 UTC
Pops up consistently. If it still happens with kernel-4.8.0-0.rc3.git0.1.fc25 I'll let upstream know about it.

Comment 3 Laura Abbott 2017-01-17 01:21:52 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 4 Laura Abbott 2017-02-23 23:03:25 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.