Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752536Ab3CUTVs (ORCPT ); Thu, 21 Mar 2013 15:21:48 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:37822 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752418Ab3CUTVr (ORCPT ); Thu, 21 Mar 2013 15:21:47 -0400 Date: Thu, 21 Mar 2013 19:21:46 +0000 From: Al Viro To: Dave Jones , Linux Kernel , Linus Torvalds Subject: Re: VFS deadlock ? Message-ID: <20130321192146.GX21522@ZenIV.linux.org.uk> References: <20130321190653.GA15479@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130321190653.GA15479@redhat.com> 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 Content-Length: 1129 Lines: 20 On Thu, Mar 21, 2013 at 03:06:53PM -0400, Dave Jones wrote: > Al, Linus, > trinity-child2 D ffff880110b3a7e0 5448 7669 1 0x00000004 [sits in rename(), trying to grab ->i_mutex on a parent] > Showing all locks held in the system: > 4 locks on stack by trinity-child2/7669: > #0: blocked: (sb_writers#4){.+.+.+}, instance: ffff8801292d17d8, at: [] mnt_want_write+0x24/0x50 > #1: held: (&type->s_vfs_rename_key){+.+.+.}, instance: ffff8801292d1928, at: [] lock_rename+0x3e/0x120 > #2: held: (&type->i_mutex_dir_key#2/1){+.+.+.}, instance: ffff880110b3a858, at: [] lock_rename+0xfe/0x120 > #3: blocked: (&type->i_mutex_dir_key#2/2){+.+.+.}, instance: ffff880110b3a858, at: [] lock_rename+0x114/0x120 Wait a minute... How the hell does it manage to sit with *two* blocked locks? Confused... -- 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/