Created attachment 947358 [details] dmesg Description of problem: Kernel throws a warning: [ 2522.813858] [ INFO: possible circular locking dependency detected ] [ 2522.813994] 3.17.0-0.rc5.git3.1.fc22.x86_64 #1 Not tainted [ 2522.814013] ------------------------------------------------------- [ 2522.814013] swift-object-au/957 is trying to acquire lock: [ 2522.814013] (&mm->mmap_sem){++++++}, at: [<ffffffff8120022e>] might_fault+0x5e/0xc0 [ 2522.814013] but task is already holding lock: [ 2522.814013] (&xfs_dir_ilock_class){.+.+..}, at: [<ffffffffa0171562>] xfs_ilock+0xf2/0x1c0 [xfs] [ 2522.814013] which lock already depends on the new lock. Please see the attached dmesg for full stack traces. Version-Release number of selected component (if applicable): How reproducible: kernel-3.17.0-0.rc5.git3.1.fc22.x86_64 Steps to Reproduce: 1. Make and mount three XFS volumes 2. Run OpenStack Swift on the XFS volumes Actual results: Warning Expected results: No warning (hopefuly fixed, not just message suppressed) Additional info: This is only a warning. The system continues to function. However, it seems like something we might want to save for the record.
This is a known false positive. Still hasn't been fixed yet. https://lkml.org/lkml/2014/1/23/642
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
*********** 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 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. 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 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.