Bug 736813 - possible circular locking (&sb->s_type->i_mutex_key#15){+.+.+.}, at: [<ffffffff811ae562>] ext4_evict_inode+0x76/0x33c
possible circular locking (&sb->s_type->i_mutex_key#15){+.+.+.}, at: [<ffffff...
Status: CLOSED DUPLICATE of bug 732572
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-09-08 14:55 EDT by David Nielsen
Modified: 2011-09-08 15:10 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-09-08 15:10:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
dmesg output (123.64 KB, text/plain)
2011-09-08 14:55 EDT, David Nielsen
no flags Details

  None (edit)
Description David Nielsen 2011-09-08 14:55:10 EDT
Created attachment 522181 [details]
dmesg output

Description of problem:

I am seeing this in dmesg booting the radeon test day image on my MacMini5.2

[   40.751991] =======================================================
[   40.751995] [ INFO: possible circular locking dependency detected ]
[   40.751998] 3.1.0-0.rc3.git0.0.fc16.x86_64 #1
[   40.752000] -------------------------------------------------------
[   40.752003] gnome-settings-/1558 is trying to acquire lock:
[   40.752005]  (&sb->s_type->i_mutex_key#15){+.+.+.}, at: [<ffffffff811ae562>] ext4_evict_inode+0x76/0x33c
[   40.752016] 
[   40.752017] but task is already holding lock:
[   40.752019]  (&mm->mmap_sem){++++++}, at: [<ffffffff81116f9a>] sys_munmap+0x3b/0x60
[   40.752026] 
[   40.752026] which lock already depends on the new lock.
[   40.752027] 
[   40.752029] 
[   40.752030] the existing dependency chain (in reverse order) is:
[   40.752032] 
[   40.752033] -> #1 (&mm->mmap_sem){++++++}:
[   40.752037]        [<ffffffff8108eff1>] lock_acquire+0xf3/0x13e
[   40.752042]        [<ffffffff8110fbd7>] might_fault+0x89/0xac
[   40.752048]        [<ffffffff81151bfb>] filldir+0x6f/0xc7
[   40.752053]        [<ffffffff811a5347>] call_filldir+0x96/0xc0
[   40.752058]        [<ffffffff811a5680>] ext4_readdir+0x1bd/0x548
[   40.752062]        [<ffffffff81151e50>] vfs_readdir+0x7b/0xb4
[   40.752066]        [<ffffffff81151f6f>] sys_getdents+0x7e/0xd1
[   40.752070]        [<ffffffff8150b082>] system_call_fastpath+0x16/0x1b
[   40.752076] 
[   40.752076] -> #0 (&sb->s_type->i_mutex_key#15){+.+.+.}:
[   40.752082]        [<ffffffff8108e81e>] __lock_acquire+0xa1a/0xcf7
[   40.752086]        [<ffffffff8108eff1>] lock_acquire+0xf3/0x13e
[   40.752089]        [<ffffffff815025db>] __mutex_lock_common+0x5d/0x39a
[   40.752094]        [<ffffffff81502a27>] mutex_lock_nested+0x40/0x45
[   40.752098]        [<ffffffff811ae562>] ext4_evict_inode+0x76/0x33c
[   40.752102]        [<ffffffff81157cf2>] evict+0x99/0x153
[   40.752106]        [<ffffffff81157f3d>] iput+0x191/0x19a
[   40.752109]        [<ffffffff81154bf5>] dentry_kill+0x123/0x145
[   40.752114]        [<ffffffff81155004>] dput+0xf7/0x107
[   40.752118]        [<ffffffff811440db>] fput+0x1dd/0x1f5
[   40.752122]        [<ffffffff811158ee>] remove_vma+0x56/0x87
[   40.752126]        [<ffffffff81116afd>] do_munmap+0x2f2/0x30b
[   40.752130]        [<ffffffff81116fa8>] sys_munmap+0x49/0x60
[   40.752133]        [<ffffffff8150b082>] system_call_fastpath+0x16/0x1b
[   40.752137] 
[   40.752138] other info that might help us debug this:
[   40.752139] 
[   40.752141]  Possible unsafe locking scenario:
[   40.752142] 
[   40.752143]        CPU0                    CPU1
[   40.752145]        ----                    ----
[   40.752147]   lock(&mm->mmap_sem);
[   40.752151]                                lock(&sb->s_type->i_mutex_key);
[   40.752154]                                lock(&mm->mmap_sem);
[   40.752158]   lock(&sb->s_type->i_mutex_key);
[   40.752161] 
[   40.752162]  *** DEADLOCK ***
[   40.752163] 
[   40.752165] 1 lock held by gnome-settings-/1558:
[   40.752167]  #0:  (&mm->mmap_sem){++++++}, at: [<ffffffff81116f9a>] sys_munmap+0x3b/0x60
[   40.752174] 
[   40.752174] stack backtrace:
[   40.752178] Pid: 1558, comm: gnome-settings- Tainted: G        W   3.1.0-0.rc3.git0.0.fc16.x86_64 #1
[   40.752180] Call Trace:
[   40.752185]  [<ffffffff814f9b74>] print_circular_bug+0x1f8/0x209
[   40.752189]  [<ffffffff8108e81e>] __lock_acquire+0xa1a/0xcf7
[   40.752193]  [<ffffffff8108be17>] ? register_lock_class+0x1e/0x2d3
[   40.752197]  [<ffffffff811ae562>] ? ext4_evict_inode+0x76/0x33c
[   40.752201]  [<ffffffff8108eff1>] lock_acquire+0xf3/0x13e
[   40.752204]  [<ffffffff811ae562>] ? ext4_evict_inode+0x76/0x33c
[   40.752208]  [<ffffffff811ae562>] ? ext4_evict_inode+0x76/0x33c
[   40.752212]  [<ffffffff815025db>] __mutex_lock_common+0x5d/0x39a
[   40.752215]  [<ffffffff811ae562>] ? ext4_evict_inode+0x76/0x33c
[   40.752220]  [<ffffffff810152af>] ? native_sched_clock+0x34/0x36
[   40.752224]  [<ffffffff810152ba>] ? sched_clock+0x9/0xd
[   40.752227]  [<ffffffff8108b885>] ? trace_hardirqs_off+0xd/0xf
[   40.752231]  [<ffffffff8108bdf0>] ? lock_release_holdtime.part.9+0x59/0x62
[   40.752235]  [<ffffffff81502a27>] mutex_lock_nested+0x40/0x45
[   40.752239]  [<ffffffff811ae562>] ext4_evict_inode+0x76/0x33c
[   40.752242]  [<ffffffff81157cf2>] evict+0x99/0x153
[   40.752246]  [<ffffffff81157f3d>] iput+0x191/0x19a
[   40.752250]  [<ffffffff81154bf5>] dentry_kill+0x123/0x145
[   40.752254]  [<ffffffff81155004>] dput+0xf7/0x107
[   40.752258]  [<ffffffff811440db>] fput+0x1dd/0x1f5
[   40.752261]  [<ffffffff811158ee>] remove_vma+0x56/0x87
[   40.752264]  [<ffffffff81116afd>] do_munmap+0x2f2/0x30b
[   40.752268]  [<ffffffff81116fa8>] sys_munmap+0x49/0x60
[   40.752272]  [<ffffffff8150b082>] system_call_fastpath+0x16/0x1b

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. install rEFIt
2. boot test day image from usb
3.
  
Actual results:
above message

Expected results:
no warnings or errors

Additional info:
Comment 1 Josh Boyer 2011-09-08 15:10:31 EDT

*** This bug has been marked as a duplicate of bug 732572 ***

Note You need to log in before you can comment on or make changes to this bug.