Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752024AbaAXB7E (ORCPT ); Thu, 23 Jan 2014 20:59:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40932 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750881AbaAXB7B (ORCPT ); Thu, 23 Jan 2014 20:59:01 -0500 Date: Thu, 23 Jan 2014 20:58:56 -0500 From: Josh Boyer To: Dave Chinner , Ben Myers Cc: sandeen@redhat.com, xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: XFS lockdep spew with v3.13-4156-g90804ed Message-ID: <20140124015855.GM16455@hansolo.jdub.homelinux.org> 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 Hi All, I'm hitting an XFS lockdep error with Linus' tree today after the XFS merge. I wasn't hitting this with v3.13-3995-g0dc3fd0, which seems to backup the "before XFS merge" claim. Full text below: [ 132.638044] ====================================================== [ 132.638045] [ INFO: possible circular locking dependency detected ] [ 132.638047] 3.14.0-0.rc0.git7.1.fc21.x86_64 #1 Not tainted [ 132.638048] ------------------------------------------------------- [ 132.638049] gnome-session/1432 is trying to acquire lock: [ 132.638050] (&mm->mmap_sem){++++++}, at: [] might_fault+0x 5f/0xb0 [ 132.638055] but task is already holding lock: [ 132.638056] (&(&ip->i_lock)->mr_lock){++++..}, at: [] xfs_ ilock+0xf2/0x1c0 [xfs] [ 132.638076] which lock already depends on the new lock. [ 132.638077] the existing dependency chain (in reverse order) is: [ 132.638078] -> #1 (&(&ip->i_lock)->mr_lock){++++..}: [ 132.638080] [] lock_acquire+0xa2/0x1d0 [ 132.638083] [] _raw_spin_lock+0x3e/0x80 [ 132.638085] [] __mark_inode_dirty+0x119/0x440 [ 132.638088] [] __set_page_dirty+0x6c/0xc0 [ 132.638090] [] mark_buffer_dirty+0x61/0x180 [ 132.638092] [] __block_commit_write.isra.21+0x81/0xb0 [ 132.638094] [] block_write_end+0x36/0x70 [ 132.638096] [] generic_write_end+0x28/0x90 [ 132.638097] [] xfs_vm_write_end+0x2b/0x70 [xfs] [ 132.638104] [] generic_file_buffered_write+0x156/0x260 [ 132.638107] [] xfs_file_buffered_aio_write+0x107/0x250 [xfs] [ 132.638115] [] xfs_file_aio_write+0xcb/0x130 [xfs] [ 132.638122] [] do_sync_write+0x5a/0x90 [ 132.638125] [] vfs_write+0xbd/0x1f0 [ 132.638126] [] SyS_write+0x4c/0xa0 [ 132.638128] [] system_call_fastpath+0x16/0x1b [ 132.638130] -> #0 (&mm->mmap_sem){++++++}: [ 132.638132] [] __lock_acquire+0x18ec/0x1aa0 [ 132.638133] [] lock_acquire+0xa2/0x1d0 [ 132.638135] [] might_fault+0x8c/0xb0 [ 132.638136] [] filldir+0x91/0x120 [ 132.638138] [] xfs_dir2_sf_getdents+0x23f/0x2a0 [xfs] [ 132.638146] [] xfs_readdir+0x16b/0x1d0 [xfs] [ 132.638154] [] xfs_file_readdir+0x2b/0x40 [xfs] [ 132.638161] [] iterate_dir+0xa8/0xe0 [ 132.638163] [] SyS_getdents+0x93/0x120 [ 132.638165] [] system_call_fastpath+0x16/0x1b [ 132.638166] other info that might help us debug this: [ 132.638167] Possible unsafe locking scenario: [ 132.638168] CPU0 CPU1 [ 132.638169] ---- ---- [ 132.638169] lock(&(&ip->i_lock)->mr_lock); [ 132.638171] lock(&mm->mmap_sem); [ 132.638172] lock(&(&ip->i_lock)->mr_lock); [ 132.638173] lock(&mm->mmap_sem); [ 132.638174] *** DEADLOCK *** [ 132.638176] 2 locks held by gnome-session/1432: [ 132.638177] #0: (&type->i_mutex_dir_key#4){+.+.+.}, at: [] iterate_dir+0x62/0xe0 [ 132.638180] #1: (&(&ip->i_lock)->mr_lock){++++..}, at: [] xfs_ilock+0xf2/0x1c0 [xfs] [ 132.638193] stack backtrace: [ 132.638195] CPU: 3 PID: 1432 Comm: gnome-session Not tainted 3.14.0-0.rc0.git7.1.fc21.x86_64 #1 [ 132.638196] Hardware name: Dell Inc. XPS 8300 /0Y2MRG, BIOS A06 10/17/2011 [ 132.638197] ffffffff825ba040 ffff88030dc75c60 ffffffff8177a8c9 ffffffff825ba040 [ 132.638199] ffff88030dc75ca0 ffffffff8177616c ffff88030dc75cf0 ffff8802fb51dba8 [ 132.638201] ffff8802fb51d010 0000000000000002 0000000000000002 ffff8802fb51dba8 [ 132.638203] Call Trace: [ 132.638205] [] dump_stack+0x4d/0x66 [ 132.638207] [] print_circular_bug+0x201/0x20f [ 132.638210] [] __lock_acquire+0x18ec/0x1aa0 [ 132.638212] [] lock_acquire+0xa2/0x1d0 [ 132.638213] [] ? might_fault+0x5f/0xb0 [ 132.638215] [] might_fault+0x8c/0xb0 [ 132.638216] [] ? might_fault+0x5f/0xb0 [ 132.638218] [] filldir+0x91/0x120 [ 132.638226] [] xfs_dir2_sf_getdents+0x23f/0x2a0 [xfs] [ 132.638237] [] ? xfs_ilock+0xf2/0x1c0 [xfs] [ 132.638245] [] xfs_readdir+0x16b/0x1d0 [xfs] [ 132.638253] [] xfs_file_readdir+0x2b/0x40 [xfs] [ 132.638255] [] iterate_dir+0xa8/0xe0 [ 132.638258] [] ? fget_light+0x3c/0x4f0 [ 132.638260] [] SyS_getdents+0x93/0x120 [ 132.638261] [] ? fillonedir+0xf0/0xf0 [ 132.638264] [] ? __audit_syscall_entry+0x9c/0xf0 [ 132.638265] [] system_call_fastpath+0x16/0x1b josh -- 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/