From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764382AbZLQUha (ORCPT ); Thu, 17 Dec 2009 15:37:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763071AbZLQUh2 (ORCPT ); Thu, 17 Dec 2009 15:37:28 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:35196 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762908AbZLQUh1 (ORCPT ); Thu, 17 Dec 2009 15:37:27 -0500 Date: Thu, 17 Dec 2009 20:37:26 +0000 From: Al Viro To: Linus Torvalds Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org Subject: Re: [revert] commit e9496ff46a20a8592fdc7bdaaf41b45eb808d310 needs to be reverted Message-ID: <20091217203726.GE18217@ZenIV.linux.org.uk> References: <1261075774.2868.16.camel@localhost> <20091217202613.GD18217@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091217202613.GD18217@ZenIV.linux.org.uk> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 17, 2009 at 08:26:13PM +0000, Al Viro wrote: > On Thu, Dec 17, 2009 at 01:49:34PM -0500, Eric Paris wrote: > > I pulled from Linus Dec16 and didn't have problems. This is a pull from > > Dec17, plus some of my own patches which I'd be surprised to learn were > > related. I have an NFS mount in my fstab, I assume this is that being > > mounted on boot. I'll start a bisect if needed, but maybe someone will > > know what they broke instantly.... > > Gyah... Please, revert e9496ff46a20a8592fdc7bdaaf41b45eb808d310; > it's dependent on a lot of other stuff not currently in mainline > and badly broken with current fs/namespace.c. Sorry, badly out-of-order > cherry-pick from old queue. PS: there's a large pending series reworking the refcounting and lifetime rules for vfsmounts that will, among other things, allow to rip a subtree away _without_ dissolving connections in it, to be garbage-collected when all active references are gone. It's considerably saner wrt "is the subtree busy" logics, but it's nowhere near being ready for merge at the moment; this changeset is one of the things becoming possible with that sucker, but it certainly shouldn't have been picked during this cycle. My apologies...