Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758777Ab2FHAmZ (ORCPT ); Thu, 7 Jun 2012 20:42:25 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:35345 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755711Ab2FHAmY convert rfc822-to-8bit (ORCPT ); Thu, 7 Jun 2012 20:42:24 -0400 MIME-Version: 1.0 In-Reply-To: <20120608003604.GK30000@ZenIV.linux.org.uk> References: <20120606230040.GA18089@redhat.com> <20120606235403.GC30000@ZenIV.linux.org.uk> <20120607002914.GB22223@redhat.com> <20120607011915.GA17566@redhat.com> <20120607012900.GE30000@ZenIV.linux.org.uk> <20120607193607.GI30000@ZenIV.linux.org.uk> <873966n2c2.fsf@xmission.com> <20120608003604.GK30000@ZenIV.linux.org.uk> From: Linus Torvalds Date: Thu, 7 Jun 2012 17:42:02 -0700 X-Google-Sender-Auth: 1sIUw4z475Fparlb4zyshj_v95M Message-ID: Subject: Re: processes hung after sys_renameat, and 'missing' processes To: Al Viro Cc: "Eric W. Biederman" , Dave Jones , Linux Kernel , Miklos Szeredi , Jan Kara , Peter Zijlstra , linux-fsdevel@vger.kernel.org, "J. Bruce Fields" , Sage Weil Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 807 Lines: 18 On Thu, Jun 7, 2012 at 5:36 PM, Al Viro wrote: > > Frankly, I would very much prefer to have the same locking rules wherever > possible. ?The locking system is already overcomplicated and making its > analysis fs-dependent as well... I do agree that it would be better if we avoid it. I was just trying to explain that the dentry locking is *not* enough, for the simple reason that it relies on upper-level non-dentry locking just to work. Your patch looks good, but whether it works I have no idea ;) Linus -- 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/