From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Kent Subject: Re: [autofs] [RFC PATCH]autofs4: hang and proposed fix Date: Mon, 5 Dec 2005 09:02:57 -0500 (EST) Message-ID: References: <438E1A05.7000308@us.ibm.com> <438F251B.7060602@us.ibm.com> <43906968.6080508@us.ibm.com> <1133547148.8976.25.camel@lade.trondhjem.org> <20051204125612.GA28229@infradead.org> <20051204125740.GB28229@infradead.org> <20051204171729.GA31111@infradead.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Trond Myklebust , Will Taber , Jeff Moyer , Ram Pai , autofs mailing list , linux-fsdevel Return-path: Received: from wombat.indigo.net.au ([202.0.185.19]:49930 "EHLO wombat.indigo.net.au") by vger.kernel.org with ESMTP id S1750718AbVLEBDk (ORCPT ); Sun, 4 Dec 2005 20:03:40 -0500 To: Christoph Hellwig In-Reply-To: <20051204171729.GA31111@infradead.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sun, 4 Dec 2005, Christoph Hellwig wrote: > On Sun, Dec 04, 2005 at 10:58:03PM +0800, Ian Kent wrote: > > > never called by the VFS. autofs (v4 at least) doesn't use it so now always > > > get a nameidata. In fact if you look in -mm there's a patch from me that > > > makes use of that fact. > > > > > > > But Will is calling it in a something like a stacking context and autofs > > fails to handle it. Hence this discussion. > > No, for current TOT that can't happen. It could happen for older kernels > but nothing is doing it in the tree anymore and if anything outside is doing > it it's fundamentally broken. > Yes. So I should continue with my focus on handling link_path_walk cases as all paths should pass through their? Ian