Bug 1402453 - [abrt] [ INFO: possible recursive locking detected ] [btrfs] [NEEDINFO]
Summary: [abrt] [ INFO: possible recursive locking detected ] [btrfs]
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:69b65ea740220e684dbeccd146e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 15:10 UTC by secondary
Modified: 2019-01-09 12:54 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-23 23:03:11 UTC
Type: ---
labbott: needinfo? (secondary)

Attachments (Terms of Use)
File: dmesg (224.51 KB, text/plain)
2016-12-07 15:10 UTC, secondary 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description secondary 2016-12-07 15:10:26 UTC 
Description of problem:
Boot the 4.9-rc8 kernel with drm-next patches applied.

Additional info:
reporter:       libreport-2.8.0
[ INFO: possible recursive locking detected ]
4.9.0-0.rc8.git0.1.fc25.x86_64 #1 Not tainted
---------------------------------------------
gvfsd-metadata/1397 is trying to acquire lock:
 (
&ei->log_mutex
){+.+...}
, at: 
[<ffffffffc05f53f2>] btrfs_log_inode+0x162/0x1190 [btrfs]

Potential duplicate: bug 1385185
Comment 1 secondary 2016-12-07 15:10:36 UTC 
Created attachment 1229089 [details]
File: dmesg
Comment 2 Laura Abbott 2017-01-17 01:13:32 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 3 Laura Abbott 2017-02-23 23:03:11 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.
Note You need to log in before you can comment on or make changes to this bug.