Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755483AbZJJXKc (ORCPT ); Sat, 10 Oct 2009 19:10:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755094AbZJJXKc (ORCPT ); Sat, 10 Oct 2009 19:10:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:61071 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755074AbZJJXKb (ORCPT ); Sat, 10 Oct 2009 19:10:31 -0400 Date: Sun, 11 Oct 2009 01:09:50 +0200 (CEST) From: John Kacur X-X-Sender: jkacur@localhost.localdomain To: linux-kernel@vger.kernel.org cc: Peter Zijlstra , Thomas Gleixner , xfs-masters@oss.sgi.com Subject: INFO: possible circular locking dependency detected Message-ID: User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3426 Lines: 79 ======================================================= [ INFO: possible circular locking dependency detected ] 2.6.32-rc3 #1 ------------------------------------------------------- mono/3284 is trying to acquire lock: (&(&ip->i_iolock)->mr_lock){++++++}, at: [] xfs_ilock+0x3a/0xa3 [xfs] but task is already holding lock: (&mm->mmap_sem){++++++}, at: [] sys_munmap+0x45/0x83 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&mm->mmap_sem){++++++}: [] __lock_acquire+0xc04/0xde2 [] lock_acquire+0xe3/0x114 [] might_fault+0x9f/0xd8 [] file_read_actor+0xdc/0x166 [] generic_file_aio_read+0x381/0x5d5 [] xfs_read+0x185/0x209 [xfs] [] xfs_file_aio_read+0x72/0x88 [xfs] [] do_sync_read+0xf9/0x152 [] vfs_read+0xbb/0x12c [] sys_read+0x56/0x93 [] system_call_fastpath+0x16/0x1b -> #0 (&(&ip->i_iolock)->mr_lock){++++++}: [] __lock_acquire+0xadc/0xde2 [] lock_acquire+0xe3/0x114 [] down_write_nested+0x57/0xa2 [] xfs_ilock+0x3a/0xa3 [xfs] [] xfs_free_eofblocks+0x115/0x21a [xfs] [] xfs_release+0x146/0x169 [xfs] [] xfs_file_release+0x23/0x3b [xfs] [] __fput+0x12a/0x1ec [] fput+0x2b/0x41 [] remove_vma+0x5f/0xad [] do_munmap+0x313/0x349 [] sys_munmap+0x53/0x83 [] system_call_fastpath+0x16/0x1b other info that might help us debug this: 1 lock held by mono/3284: #0: (&mm->mmap_sem){++++++}, at: [] sys_munmap+0x45/0x83 stack backtrace: Pid: 3284, comm: mono Not tainted 2.6.32-rc3 #1 Call Trace: [] print_circular_bug+0xc2/0xe7 [] __lock_acquire+0xadc/0xde2 [] ? xfs_ilock+0x3a/0xa3 [xfs] [] ? xfs_ilock+0x3a/0xa3 [xfs] [] lock_acquire+0xe3/0x114 [] ? xfs_ilock+0x3a/0xa3 [xfs] [] down_write_nested+0x57/0xa2 [] ? xfs_ilock+0x3a/0xa3 [xfs] [] ? xfs_trans_alloc+0xa7/0xc8 [xfs] [] xfs_ilock+0x3a/0xa3 [xfs] [] xfs_free_eofblocks+0x115/0x21a [xfs] [] ? get_parent_ip+0x20/0x67 [] xfs_release+0x146/0x169 [xfs] [] xfs_file_release+0x23/0x3b [xfs] [] __fput+0x12a/0x1ec [] ? tlb_finish_mmu+0x6c/0x90 [] fput+0x2b/0x41 [] remove_vma+0x5f/0xad [] do_munmap+0x313/0x349 [] ? down_write+0x80/0x9d [] sys_munmap+0x53/0x83 [] system_call_fastpath+0x16/0x1b -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/