Skip to contentSkip to conversation

INFO: inconsistent lock state

BUG Srivatsa S. Bhat 2 participants 4 messages Sep 20, 2011 – Sep 26, 2011 VFS

lore
Share & tools
lore
#0 lore raw

Hi,

While running kernel compilation along with suspend/resume tests using the pm_test framework (at the processors level), lockdep reports inconsistent lock state.
This is with Kernel 3.0.4.

Excerpt of the log:
kernel: [ 8221.176651] Freezing user space processes ... (elapsed 0.01 seconds) done.
kernel: [ 8221.247173] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
kernel: [ 8221.321962] PM: Preallocating image memory...
kernel: [ 8221.768104] =================================
kernel: [ 8221.806233] [ INFO: inconsistent lock state ]
kernel: [ 8221.842744] 3.0.4 #1
kernel: [ 8221.861076] ---------------------------------
kernel: [ 8221.897583] inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage.
kernel: [ 8221.952270] test_processors/5971 [HC0[0]:SC0[0]:HE1:SE1] takes:
kernel: [ 8222.001872] (&sb->s_type->i_mutex_key#13){+.+.?.}, at: [<ffffffffa01262ee>] ext4_evict_inode+0x2e/0x3d0 [ext4]
kernel: [ 8222.086774] {RECLAIM_FS-ON-W} state was registered at:
kernel: [ 8222.129821] [<ffffffff810a6033>] mark_held_locks+0x73/0xa0
kernel: [ 8222.177316] [<ffffffff810a60ff>] lockdep_trace_alloc+0x9f/0xd0
kernel: [ 8222.227720] [<ffffffff81164dd6>] kmem_cache_alloc+0x36/0x1f0
kernel: [ 8222.276675] [<ffffffff81191927>] d_alloc+0x27/0x1d0
kernel: [ 8222.319078] [<ffffffff811864dd>] d_alloc_and_lookup+0x2d/0x90
kernel: [ 8222.368755] [<ffffffff81188473>] do_lookup+0x2b3/0x300
kernel: [ 8222.413340] [<ffffffff8118983f>] link_path_walk+0x18f/0x930
kernel: [ 8222.461564] [<ffffffff8118a665>] path_lookupat+0x55/0x690
kernel: [ 8222.508330] [<ffffffff8118acd1>] do_path_lookup+0x31/0xc0
kernel: [ 8222.555098] [<ffffffff8118b9c9>] user_path_at+0x59/0xa0
kernel: [ 8222.600413] [<ffffffff8118018c>] vfs_fstatat+0x4c/0x90
kernel: [ 8222.645001] [<ffffffff811802fb>] vfs_stat+0x1b/0x20
kernel: [ 8222.687397] [<ffffffff81180324>] sys_newstat+0x24/0x50
kernel: [ 8222.731986] [<ffffffff8152fa82>] system_call_fastpath+0x16/0x1b
kernel: [ 8222.783119] irq event stamp: 2109279487
kernel: [ 8222.815258] hardirqs last enabled at (2109279487): [<ffffffff81526fe0>] _raw_spin_unlock_irq+0x30/0x40
kernel: [ 8222.894087] hardirqs last disabled at (2109279486): [<ffffffff8152665f>] _raw_spin_lock_irq+0x1f/0x80
kernel: [ 8222.971464] softirqs last enabled at (2109279484): [<ffffffff8106ea7c>] __do_softirq+0x14c/0x250
kernel: [ 8223.045929] softirqs last disabled at (2109279461): [<ffffffff81530d3c>] call_softirq+0x1c/0x30
kernel: [ 8223.118941]
kernel: [ 8223.118942] other info that might help us debug this:
kernel: [ 8223.173776] Possible unsafe locking scenario:
kernel: [ 8223.173777]
kernel: [ 8223.223525] CPU0
kernel: [ 8223.244031] ----
kernel: [ 8223.264541] lock(&sb->s_type->i_mutex_key);
kernel: [ 8223.301204] <Interrupt>
kernel: [ 8223.323168] lock(&sb->s_type->i_mutex_key);
kernel: [ 8223.361284]
kernel: [ 8223.361285] *** DEADLOCK ***
kernel: [ 8223.361285]
kernel: [ 8223.411172] 5 locks held by test_processors/5971:
kernel: [ 8223.450586] #0: (&buffer->mutex){+.+.+.}, at: [<ffffffff811ee0a4>] sysfs_write_file+0x44/0x170
kernel: [ 8223.524561] #1: (s_active#79){.+.+.+}, at: [<ffffffff811ee12d>] sysfs_write_file+0xcd/0x170
kernel: [ 8223.596444] #2: (pm_mutex){+.+.+.}, at: [<ffffffff810b8a7c>] hibernate+0x1c/0x200
kernel: [ 8223.660968] #3: (shrinker_rwsem){++++..}, at: [<ffffffff8112b98d>] shrink_slab+0x3d/0x1b0
kernel: [ 8223.731320] #4: (iprune_sem){.+.+.-}, at: [<ffffffff81196cc1>] prune_icache+0x31/0x310
kernel: [ 8223.799493]
kernel: [ 8223.799493] stack backtrace:
kernel: [ 8223.836149] Pid: 5971, comm: test_processors Not tainted 3.0.4 #1
kernel: [ 8223.887194] Call Trace:
kernel: [ 8223.907706] [<ffffffff810a5439>] print_usage_bug+0x179/0x180
kernel: [ 8223.955846] [<ffffffff810a5440>] ? print_usage_bug+0x180/0x180
kernel: [ 8224.005444] [<ffffffff810a5aae>] mark_lock_irq+0xfe/0x290
kernel: [ 8224.051402] [<ffffffff810a5d91>] mark_lock+0x151/0x1f0
kernel: [ 8224.095182] [<ffffffff810a5ef6>] mark_irqflags+0xc6/0x190
kernel: [ 8224.141139] [<ffffffff810a7624>] __lock_acquire+0x344/0x4f0
kernel: [ 8224.188555] [<ffffffff810a7e84>] lock_acquire+0xa4/0x130
kernel: [ 8224.233792] [<ffffffffa01262ee>] ? ext4_evict_inode+0x2e/0x3d0 [ext4]
kernel: [ 8224.288477] [<ffffffff81524fed>] __mutex_lock_common+0x4d/0x3f0
kernel: [ 8224.338805] [<ffffffffa01262ee>] ? ext4_evict_inode+0x2e/0x3d0 [ext4]
kernel: [ 8224.393486] [<ffffffff810a190d>] ? trace_hardirqs_off+0xd/0x10
kernel: [ 8224.443082] [<ffffffff8109439f>] ? local_clock+0x6f/0x80
kernel: [ 8224.488323] [<ffffffffa01262ee>] ? ext4_evict_inode+0x2e/0x3d0 [ext4]
kernel: [ 8224.543012] [<ffffffff810a5865>] ? lock_release_holdtime+0x35/0x180
kernel: [ 8224.596243] [<ffffffff810a7c99>] ? __lock_release+0x129/0x190
kernel: [ 8224.645122] [<ffffffff811966d5>] ? evict+0x75/0x180
kernel: [ 8224.686721] [<ffffffff815254fa>] mutex_lock_nested+0x4a/0x60
kernel: [ 8224.734871] [<ffffffffa01262ee>] ext4_evict_inode+0x2e/0x3d0 [ext4]
kernel: [ 8224.788104] [<ffffffff811966e3>] evict+0x83/0x180
kernel: [ 8224.828248] [<ffffffff81196827>] dispose_list+0x47/0x60
kernel: [ 8224.872752] [<ffffffff81196de5>] prune_icache+0x155/0x310
kernel: [ 8224.918708] [<ffffffff81196fe6>] shrink_icache_memory+0x46/0x50
kernel: [ 8224.969034] [<ffffffff8112ba82>] shrink_slab+0x132/0x1b0
kernel: [ 8225.014268] [<ffffffff8112db02>] do_try_to_free_pages+0x2d2/0x3c0
kernel: [ 8225.066044] [<ffffffff8112dcad>] shrink_all_memory+0xbd/0xf0
kernel: [ 8225.114192] [<ffffffff81136d76>] ? next_online_pgdat+0x26/0x50
kernel: [ 8225.163789] [<ffffffff810ba6a5>] hibernate_preallocate_memory+0x1e5/0x2a0
kernel: [ 8225.221379] [<ffffffff810b896d>] hibernation_snapshot+0x8d/0x180
kernel: [ 8225.272424] [<ffffffff810b8b58>] hibernate+0xf8/0x200
kernel: [ 8225.315476] [<ffffffff810b6ffc>] state_store+0xec/0x100
kernel: [ 8225.359984] [<ffffffff8125f8b7>] kobj_attr_store+0x17/0x20
kernel: [ 8225.406670] [<ffffffff811ee146>] sysfs_write_file+0xe6/0x170
kernel: [ 8225.454809] [<ffffffff8117afd0>] vfs_write+0xd0/0x1a0
kernel: [ 8225.497856] [<ffffffff8117b1a4>] sys_write+0x54/0xa0
kernel: [ 8225.540180] [<ffffffff8152fa82>] system_call_fastpath+0x16/0x1b
kernel: [ 8226.890288] done (allocated 2511433 pages)
kernel: [ 8226.924630] PM: Allocated 10045732 kbytes in 5.54 seconds (1813.30 MB/s)

Signature · 4 lines
Regards,
Srivatsa S. Bhat  <[email protected]>
Linux Technology Center,
IBM India Systems and Technology Lab
#1 lore raw
Quoted 4 lines · Srivatsa S. Bhat

While running kernel compilation along with suspend/resume tests using the pm_test framework (at the processors level), lockdep reports inconsistent lock state.
This is with Kernel 3.0.4.

Something very similar happened to be in the logs of a machine running v3.0.4 too. It happened a few days ago (but I missed it initially). I have no idea what triggered this:

kernel: [ 3501.569697]
kernel: [ 3501.569699] =================================
kernel: [ 3501.569703] [ INFO: inconsistent lock state ]
kernel: [ 3501.569706] 3.0.4-local0.fc14.x86_64 #1
kernel: [ 3501.569708] ---------------------------------
kernel: [ 3501.569711] inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage.
kernel: [ 3501.569714] kswapd0/25 [HC0[0]:SC0[0]:HE1:SE1] takes:
kernel: [ 3501.569717] (&sb->s_type->i_mutex_key#13){+.+.?.}, at: [<ffffffff811b08eb>] ext4_evict_inode+0x41/0x255
kernel: [ 3501.569728] {RECLAIM_FS-ON-W} state was registered at:
kernel: [ 3501.569730] [<ffffffff8108fcd1>] mark_held_locks+0x50/0x72
kernel: [ 3501.569736] [<ffffffff81090273>] lockdep_trace_alloc+0xa2/0xc6
kernel: [ 3501.569740] [<ffffffff811302da>] slab_pre_alloc_hook+0x1e/0x54
kernel: [ 3501.569745] [<ffffffff81132f3d>] kmem_cache_alloc+0x25/0x105
kernel: [ 3501.569749] [<ffffffff81155a26>] d_alloc+0x27/0x1b3
kernel: [ 3501.569754] [<ffffffff8114c785>] d_alloc_and_lookup+0x2c/0x6d
kernel: [ 3501.569758] [<ffffffff8114db93>] walk_component+0x1ea/0x3da
kernel: [ 3501.569762] [<ffffffff8114eda2>] link_path_walk+0x18a/0x477
kernel: [ 3501.569766] [<ffffffff8114f1a5>] path_lookupat+0x59/0x34b
kernel: [ 3501.569770] [<ffffffff8114f4c1>] do_path_lookup+0x2a/0x99
kernel: [ 3501.569774] [<ffffffff8114f8fb>] user_path_at+0x56/0x93
kernel: [ 3501.569778] [<ffffffff81147227>] vfs_fstatat+0x49/0x74
kernel: [ 3501.569782] [<ffffffff8114728d>] vfs_stat+0x1b/0x1d
kernel: [ 3501.569786] [<ffffffff811473a3>] sys_newstat+0x1f/0x39
kernel: [ 3501.569790] [<ffffffff814f62c2>] system_call_fastpath+0x16/0x1b
kernel: [ 3501.569796] irq event stamp: 2656001
kernel: [ 3501.569798] hardirqs last enabled at (2656001): [<ffffffff814efa54>] restore_args+0x0/0x30
kernel: [ 3501.569803] hardirqs last disabled at (2655999): [<ffffffff810632a8>] __do_softirq+0x15c/0x1ed
kernel: [ 3501.569809] softirqs last enabled at (2656000): [<ffffffff810632df>] __do_softirq+0x193/0x1ed
kernel: [ 3501.569813] softirqs last disabled at (2654505): [<ffffffff814f755c>] call_softirq+0x1c/0x30
kernel: [ 3501.569818]
kernel: [ 3501.569819] other info that might help us debug this:
kernel: [ 3501.569821] Possible unsafe locking scenario:
kernel: [ 3501.569822]
kernel: [ 3501.569824] CPU0
kernel: [ 3501.569826] ----
kernel: [ 3501.569827] lock(&sb->s_type->i_mutex_key);
kernel: [ 3501.569831] <Interrupt>
kernel: [ 3501.569833] lock(&sb->s_type->i_mutex_key);
kernel: [ 3501.569836]
kernel: [ 3501.569837] *** DEADLOCK ***
kernel: [ 3501.569837]
kernel: [ 3501.569840] 2 locks held by kswapd0/25:
kernel: [ 3501.569842] #0: (shrinker_rwsem){++++..}, at: [<ffffffff81101fc9>] shrink_slab+0x3d/0x189
kernel: [ 3501.569850] #1: (iprune_sem){++++.-}, at: [<ffffffff81158be2>] shrink_icache_memory+0x50/0x288
kernel: [ 3501.569857]
kernel: [ 3501.569858] stack backtrace:
kernel: [ 3501.569861] Pid: 25, comm: kswapd0 Not tainted 3.0.4-local0.fc14.x86_64 #1
kernel: [ 3501.569863] Call Trace:
kernel: [ 3501.569868] [<ffffffff8108e538>] valid_state+0x215/0x227
kernel: [ 3501.569873] [<ffffffff8108dd2e>] ? print_irq_inversion_bug+0x1c4/0x1c4
kernel: [ 3501.569876] [<ffffffff8108e62c>] mark_lock+0xe2/0x1d8
kernel: [ 3501.569880] [<ffffffff8108eafc>] __lock_acquire+0x3da/0xdd8
kernel: [ 3501.569885] [<ffffffff8108fcd1>] ? mark_held_locks+0x50/0x72
kernel: [ 3501.569889] [<ffffffff814efa54>] ? retint_restore_args+0x13/0x13
kernel: [ 3501.569892] [<ffffffff81158869>] ? evict+0x4f/0x127
kernel: [ 3501.569896] [<ffffffff8108fdfe>] ? trace_hardirqs_on_caller+0x10b/0x12f
kernel: [ 3501.569900] [<ffffffff811b08eb>] ? ext4_evict_inode+0x41/0x255
kernel: [ 3501.569904] [<ffffffff8108f9c6>] lock_acquire+0xb7/0xfb
kernel: [ 3501.569908] [<ffffffff811b08eb>] ? ext4_evict_inode+0x41/0x255
kernel: [ 3501.569912] [<ffffffff811b08eb>] ? ext4_evict_inode+0x41/0x255
kernel: [ 3501.569916] [<ffffffff814edb1f>] __mutex_lock_common+0x4c/0x361
kernel: [ 3501.569920] [<ffffffff811b08eb>] ? ext4_evict_inode+0x41/0x255
kernel: [ 3501.569924] [<ffffffff8108be8d>] ? trace_hardirqs_off+0xd/0xf
kernel: [ 3501.569928] [<ffffffff810802da>] ? local_clock+0x36/0x4d
kernel: [ 3501.569932] [<ffffffff8108c123>] ? lock_release_holdtime+0x54/0x5b
kernel: [ 3501.569936] [<ffffffff814edf43>] mutex_lock_nested+0x40/0x45
kernel: [ 3501.569940] [<ffffffff811b08eb>] ext4_evict_inode+0x41/0x255
kernel: [ 3501.569944] [<ffffffff81158899>] evict+0x7f/0x127
kernel: [ 3501.569947] [<ffffffff8115897f>] dispose_list+0x3e/0x50
kernel: [ 3501.569951] [<ffffffff81158dea>] shrink_icache_memory+0x258/0x288
kernel: [ 3501.569955] [<ffffffff81101fc9>] ? shrink_slab+0x3d/0x189
kernel: [ 3501.569958] [<ffffffff8110207e>] shrink_slab+0xf2/0x189
kernel: [ 3501.569962] [<ffffffff81104995>] balance_pgdat+0x2f7/0x5d3
kernel: [ 3501.569967] [<ffffffff81104f3f>] kswapd+0x2ce/0x314
kernel: [ 3501.569971] [<ffffffff8107a76a>] ? wake_up_bit+0x2a/0x2a
kernel: [ 3501.569975] [<ffffffff81104c71>] ? balance_pgdat+0x5d3/0x5d3
kernel: [ 3501.569978] [<ffffffff8107a25c>] kthread+0xa0/0xa8
kernel: [ 3501.569983] [<ffffffff8108fdfe>] ? trace_hardirqs_on_caller+0x10b/0x12f
kernel: [ 3501.569987] [<ffffffff814f7464>] kernel_thread_helper+0x4/0x10
kernel: [ 3501.569991] [<ffffffff814efa54>] ? retint_restore_args+0x13/0x13
kernel: [ 3501.569995] [<ffffffff8107a1bc>] ? __init_kthread_worker+0x5b/0x5b
kernel: [ 3501.569999] [<ffffffff814f7460>] ? gs_change+0x13/0x13

Paul Bolle

#2 lore raw
Quoted 4 lines · Paul Bolle

Something very similar happened to be in the logs of a machine running v3.0.4 too. It happened a few days ago (but I missed it initially). I have no idea what triggered this:

Quoted 9 lines

kernel: [ 3501.569697]
kernel: [ 3501.569699] =================================
kernel: [ 3501.569703] [ INFO: inconsistent lock state ]
kernel: [ 3501.569706] 3.0.4-local0.fc14.x86_64 #1
kernel: [ 3501.569708] ---------------------------------
kernel: [ 3501.569711] inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage.
kernel: [ 3501.569714] kswapd0/25 [HC0[0]:SC0[0]:HE1:SE1] takes:
kernel: [ 3501.569717] (&sb->s_type->i_mutex_key#13){+.+.?.}, at: [<ffffffff811b08eb>] ext4_evict_inode+0x41/0x255 [...]

A bit of background: ext4_evict_inode+0x41 should be the call to mutex_lock() in ext4_evict_inode():

(gdb) disass /m ext4_evict_inode+48,+17
Dump of assembler code from 0xffffffff811b08da to 0xffffffff811b08eb:
193 mutex_lock(&inode->i_mutex);

   0xffffffff811b08da <ext4_evict_inode+48>:	lea    0x80(%rbx),%r12
   0xffffffff811b08e1 <ext4_evict_inode+55>:	xor    %esi,%esi
   0xffffffff811b08e3 <ext4_evict_inode+57>:	mov    %r12,%rdi
   0xffffffff811b08e6 <ext4_evict_inode+60>:	callq  0xffffffff814edf03 <mutex_lock_nested>

End of assembler dump.

That call to mutex_lock() and the following call to mutex_unlock() was added by the backport of commit 2581fdc8 ("ext4: call ext4_ioend_wait and ext4_flush_completed_IO in ext4_evict_inode") to v3.0 in the v3.0.4 patch.

Paul Bolle

#3 lore raw
In reply to Paul Bolle
Quoted 84 lines · Paul Bolle
Quoted 4 lines · Srivatsa S. Bhat

While running kernel compilation along with suspend/resume tests using the pm_test framework (at the processors level), lockdep reports inconsistent lock state.
This is with Kernel 3.0.4.

Something very similar happened to be in the logs of a machine running v3.0.4 too. It happened a few days ago (but I missed it initially). I have no idea what triggered this:

kernel: [ 3501.569697]
kernel: [ 3501.569699] =================================
kernel: [ 3501.569703] [ INFO: inconsistent lock state ]
kernel: [ 3501.569706] 3.0.4-local0.fc14.x86_64 #1
kernel: [ 3501.569708] ---------------------------------
kernel: [ 3501.569711] inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage.
kernel: [ 3501.569714] kswapd0/25 [HC0[0]:SC0[0]:HE1:SE1] takes:
kernel: [ 3501.569717] (&sb->s_type->i_mutex_key#13){+.+.?.}, at: [<ffffffff811b08eb>] ext4_evict_inode+0x41/0x255
kernel: [ 3501.569728] {RECLAIM_FS-ON-W} state was registered at:
kernel: [ 3501.569730] [<ffffffff8108fcd1>] mark_held_locks+0x50/0x72
kernel: [ 3501.569736] [<ffffffff81090273>] lockdep_trace_alloc+0xa2/0xc6
kernel: [ 3501.569740] [<ffffffff811302da>] slab_pre_alloc_hook+0x1e/0x54
kernel: [ 3501.569745] [<ffffffff81132f3d>] kmem_cache_alloc+0x25/0x105
kernel: [ 3501.569749] [<ffffffff81155a26>] d_alloc+0x27/0x1b3
kernel: [ 3501.569754] [<ffffffff8114c785>] d_alloc_and_lookup+0x2c/0x6d
kernel: [ 3501.569758] [<ffffffff8114db93>] walk_component+0x1ea/0x3da
kernel: [ 3501.569762] [<ffffffff8114eda2>] link_path_walk+0x18a/0x477
kernel: [ 3501.569766] [<ffffffff8114f1a5>] path_lookupat+0x59/0x34b
kernel: [ 3501.569770] [<ffffffff8114f4c1>] do_path_lookup+0x2a/0x99
kernel: [ 3501.569774] [<ffffffff8114f8fb>] user_path_at+0x56/0x93
kernel: [ 3501.569778] [<ffffffff81147227>] vfs_fstatat+0x49/0x74
kernel: [ 3501.569782] [<ffffffff8114728d>] vfs_stat+0x1b/0x1d
kernel: [ 3501.569786] [<ffffffff811473a3>] sys_newstat+0x1f/0x39
kernel: [ 3501.569790] [<ffffffff814f62c2>] system_call_fastpath+0x16/0x1b
kernel: [ 3501.569796] irq event stamp: 2656001
kernel: [ 3501.569798] hardirqs last enabled at (2656001): [<ffffffff814efa54>] restore_args+0x0/0x30
kernel: [ 3501.569803] hardirqs last disabled at (2655999): [<ffffffff810632a8>] __do_softirq+0x15c/0x1ed
kernel: [ 3501.569809] softirqs last enabled at (2656000): [<ffffffff810632df>] __do_softirq+0x193/0x1ed
kernel: [ 3501.569813] softirqs last disabled at (2654505): [<ffffffff814f755c>] call_softirq+0x1c/0x30
kernel: [ 3501.569818]
kernel: [ 3501.569819] other info that might help us debug this:
kernel: [ 3501.569821] Possible unsafe locking scenario:
kernel: [ 3501.569822]
kernel: [ 3501.569824] CPU0
kernel: [ 3501.569826] ----
kernel: [ 3501.569827] lock(&sb->s_type->i_mutex_key);
kernel: [ 3501.569831] <Interrupt>
kernel: [ 3501.569833] lock(&sb->s_type->i_mutex_key);
kernel: [ 3501.569836]
kernel: [ 3501.569837] *** DEADLOCK ***
kernel: [ 3501.569837]
kernel: [ 3501.569840] 2 locks held by kswapd0/25:
kernel: [ 3501.569842] #0: (shrinker_rwsem){++++..}, at: [<ffffffff81101fc9>] shrink_slab+0x3d/0x189
kernel: [ 3501.569850] #1: (iprune_sem){++++.-}, at: [<ffffffff81158be2>] shrink_icache_memory+0x50/0x288
kernel: [ 3501.569857]
kernel: [ 3501.569858] stack backtrace:
kernel: [ 3501.569861] Pid: 25, comm: kswapd0 Not tainted 3.0.4-local0.fc14.x86_64 #1
kernel: [ 3501.569863] Call Trace:
kernel: [ 3501.569868] [<ffffffff8108e538>] valid_state+0x215/0x227
kernel: [ 3501.569873] [<ffffffff8108dd2e>] ? print_irq_inversion_bug+0x1c4/0x1c4
kernel: [ 3501.569876] [<ffffffff8108e62c>] mark_lock+0xe2/0x1d8
kernel: [ 3501.569880] [<ffffffff8108eafc>] __lock_acquire+0x3da/0xdd8
kernel: [ 3501.569885] [<ffffffff8108fcd1>] ? mark_held_locks+0x50/0x72
kernel: [ 3501.569889] [<ffffffff814efa54>] ? retint_restore_args+0x13/0x13
kernel: [ 3501.569892] [<ffffffff81158869>] ? evict+0x4f/0x127
kernel: [ 3501.569896] [<ffffffff8108fdfe>] ? trace_hardirqs_on_caller+0x10b/0x12f
kernel: [ 3501.569900] [<ffffffff811b08eb>] ? ext4_evict_inode+0x41/0x255
kernel: [ 3501.569904] [<ffffffff8108f9c6>] lock_acquire+0xb7/0xfb
kernel: [ 3501.569908] [<ffffffff811b08eb>] ? ext4_evict_inode+0x41/0x255
kernel: [ 3501.569912] [<ffffffff811b08eb>] ? ext4_evict_inode+0x41/0x255
kernel: [ 3501.569916] [<ffffffff814edb1f>] __mutex_lock_common+0x4c/0x361
kernel: [ 3501.569920] [<ffffffff811b08eb>] ? ext4_evict_inode+0x41/0x255
kernel: [ 3501.569924] [<ffffffff8108be8d>] ? trace_hardirqs_off+0xd/0xf
kernel: [ 3501.569928] [<ffffffff810802da>] ? local_clock+0x36/0x4d
kernel: [ 3501.569932] [<ffffffff8108c123>] ? lock_release_holdtime+0x54/0x5b
kernel: [ 3501.569936] [<ffffffff814edf43>] mutex_lock_nested+0x40/0x45
kernel: [ 3501.569940] [<ffffffff811b08eb>] ext4_evict_inode+0x41/0x255
kernel: [ 3501.569944] [<ffffffff81158899>] evict+0x7f/0x127
kernel: [ 3501.569947] [<ffffffff8115897f>] dispose_list+0x3e/0x50
kernel: [ 3501.569951] [<ffffffff81158dea>] shrink_icache_memory+0x258/0x288
kernel: [ 3501.569955] [<ffffffff81101fc9>] ? shrink_slab+0x3d/0x189
kernel: [ 3501.569958] [<ffffffff8110207e>] shrink_slab+0xf2/0x189
kernel: [ 3501.569962] [<ffffffff81104995>] balance_pgdat+0x2f7/0x5d3
kernel: [ 3501.569967] [<ffffffff81104f3f>] kswapd+0x2ce/0x314

Quoted 8 lines

kernel: [ 3501.569971] [<ffffffff8107a76a>] ? wake_up_bit+0x2a/0x2a
kernel: [ 3501.569975] [<ffffffff81104c71>] ? balance_pgdat+0x5d3/0x5d3
kernel: [ 3501.569978] [<ffffffff8107a25c>] kthread+0xa0/0xa8
kernel: [ 3501.569983] [<ffffffff8108fdfe>] ? trace_hardirqs_on_caller+0x10b/0x12f
kernel: [ 3501.569987] [<ffffffff814f7464>] kernel_thread_helper+0x4/0x10
kernel: [ 3501.569991] [<ffffffff814efa54>] ? retint_restore_args+0x13/0x13
kernel: [ 3501.569995] [<ffffffff8107a1bc>] ? __init_kthread_worker+0x5b/0x5b
kernel: [ 3501.569999] [<ffffffff814f7460>] ? gs_change+0x13/0x13

Hi Paul,
The issue that you and I encountered seems to have some similarity with the one reported in http://www.spinics.net/lists/linux-ext4/msg27273.html

I am wondering if this warning is also a false positive like that in XFS. I am CC'ing the linux-ext4 and linux-fsdevel mailing lists.

Signature · 4 lines
Regards,
Srivatsa S. Bhat  <[email protected]>
Linux Technology Center,
IBM India Systems and Technology Lab