Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755254Ab2FCXkq (ORCPT ); Sun, 3 Jun 2012 19:40:46 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:52909 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755173Ab2FCXkp (ORCPT ); Sun, 3 Jun 2012 19:40:45 -0400 Date: Mon, 4 Jun 2012 00:40:42 +0100 From: Al Viro To: Linus Torvalds Cc: Dave Jones , Linux Kernel Subject: Re: processes hung after sys_renameat, and 'missing' processes Message-ID: <20120603234042.GR30000@ZenIV.linux.org.uk> References: <20120603223617.GB7707@redhat.com> <20120603231709.GP30000@ZenIV.linux.org.uk> <20120603232820.GQ30000@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120603232820.GQ30000@ZenIV.linux.org.uk> 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: 968 Lines: 20 On Mon, Jun 04, 2012 at 12:28:20AM +0100, Al Viro wrote: > Everything in lock_rename() appears to be at lock_rename+0x3e. Unless > there's a really huge amount of filesystems on that box, this has to > be > mutex_lock_nested(&p1->d_inode->i_mutex, I_MUTEX_PARENT); > and everything on that sucker is not holding any locks yet. IOW, that's > the tail hanging off whatever deadlock is there. Er... After another look, probably not - it's ->s_vfs_rename_mutex, so we are seeing one cross-directory rename stuck on something with all subsequent ones blocked on attempt to grab said mutex. The interesting one is the guy stuck at lock_rename+0xc9/0xf0, everything else in lock_rename() is the consequence. -- 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/