From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756092Ab0JKUKO (ORCPT ); Mon, 11 Oct 2010 16:10:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17400 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755940Ab0JKUKM (ORCPT ); Mon, 11 Oct 2010 16:10:12 -0400 Date: Mon, 11 Oct 2010 16:10:07 -0400 From: Dave Jones To: Linux Kernel Cc: selinux@gmail.com Subject: 2.6.36-rc7: inconsistent lock state: inconsistent {IN-RECLAIM_FS-R} -> {RECLAIM_FS-ON-W} usage. Message-ID: <20101011201007.GA29707@redhat.com> Mail-Followup-To: Dave Jones , Linux Kernel , selinux@gmail.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We got this report from a Fedora user (cc'd) today.. Dave > Noticed this when I tried to 'unmount/safely remove' a LUKS encrypted USB hard drive > > ================================= > [ 4960.442217] [ INFO: inconsistent lock state ] > [ 4960.442238] 2.6.36-0.35.rc7.git0.fc15.x86_64 #1 > [ 4960.442258] --------------------------------- > [ 4960.442278] inconsistent {IN-RECLAIM_FS-R} -> {RECLAIM_FS-ON-W} usage. > [ 4960.442323] umount/8522 [HC0[0]:SC0[0]:HE1:SE1] takes: > [ 4960.442350] (iprune_sem){+++++-}, at: [] invalidate_inodes+0x3e/0x12c > [ 4960.442402] {IN-RECLAIM_FS-R} state was registered at: > [ 4960.442427] [] __lock_acquire+0x3f2/0xd79 > [ 4960.442464] [] lock_acquire+0xd2/0xfd > [ 4960.442499] [] down_read+0x51/0x84 > [ 4960.442533] [] shrink_icache_memory+0x4e/0x1ee > [ 4960.442571] [] shrink_slab+0xe0/0x166 > [ 4960.442606] [] balance_pgdat+0x257/0x3fe > [ 4960.442641] [] kswapd+0x236/0x24c > [ 4960.442671] [] kthread+0x9d/0xa5 > [ 4960.442699] [] kernel_thread_helper+0x4/0x10 > [ 4960.442733] irq event stamp: 5383 > [ 4960.442747] hardirqs last enabled at (5383): [] _raw_spin_unlock_irq+0x30/0x3a > [ 4960.442801] hardirqs last disabled at (5382): [] _raw_spin_lock_irq+0x21/0x75 > [ 4960.442855] softirqs last enabled at (5358): [] bdi_queue_work+0xc1/0xca > [ 4960.442907] softirqs last disabled at (5354): [] _raw_spin_lock_bh+0x1c/0x6e > [ 4960.442959] > [ 4960.442959] other info that might help us debug this: > [ 4960.442991] 3 locks held by umount/8522: > [ 4960.443011] #0: (&type->s_umount_key#34){+++++.}, at: [] deactivate_super+0x32/0x3e > [ 4960.443063] #1: (iprune_sem){+++++-}, at: [] invalidate_inodes+0x3e/0x12c > [ 4960.443063] #2: (&fsnotify_mark_srcu){.+.+.+}, at: [] fsnotify+0x7e/0x3d7 > [ 4960.443063] > [ 4960.443063] stack backtrace: > [ 4960.443063] Pid: 8522, comm: umount Not tainted 2.6.36-0.35.rc7.git0.fc15.x86_64 #1 > [ 4960.443063] Call Trace: > [ 4960.443063] [] valid_state+0x17c/0x18e > [ 4960.443063] [] ? check_usage_backwards+0x0/0x81 > [ 4960.443063] [] mark_lock+0x11d/0x1d8 > [ 4960.443063] [] mark_held_locks+0x50/0x72 > [ 4960.443063] [] lockdep_trace_alloc+0xa2/0xc5 > [ 4960.443063] [] kmem_cache_alloc+0x36/0x159 > [ 4960.443063] [] ? fsnotify_create_event+0x3f/0x1bc > [ 4960.444138] [] fsnotify_create_event+0x3f/0x1bc > [ 4960.444138] [] send_to_group+0x159/0x1fc > [ 4960.444138] [] ? lock_acquire+0xee/0xfd > [ 4960.444138] [] ? fsnotify+0x7e/0x3d7 > [ 4960.444138] [] fsnotify+0x279/0x3d7 > [ 4960.449291] [] fsnotify_unmount_inodes+0xbb/0xfe > [ 4960.449291] [] invalidate_inodes+0x52/0x12c > [ 4960.449291] [] ? __sync_blockdev+0x32/0x34 > [ 4960.449291] [] generic_shutdown_super+0x4c/0xe1 > [ 4960.449291] [] kill_block_super+0x27/0x3f > [ 4960.449291] [] deactivate_locked_super+0x26/0x46 > [ 4960.449291] [] deactivate_super+0x3a/0x3e > [ 4960.449291] [] mntput_no_expire+0xa7/0xd3 > [ 4960.449291] [] sys_umount+0x2cf/0x301 > [ 4960.449291] [] ? trace_hardirqs_on_caller+0x10b/0x12f > [ 4960.459556] []> system_call_fastpath+0x16/0x1b