From mboxrd@z Thu Jan 1 00:00:00 1970 From: Will Taber Subject: Re: [autofs] [RFC PATCH]autofs4: hang and proposed fix Date: Wed, 07 Dec 2005 09:52:04 -0500 Message-ID: <4396F714.1010407@us.ibm.com> References: <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> <17302.157.540958.723305@segfault.boston.redhat.com> <20051206214033.GA31000@infradead.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051206214033.GA31000@infradead.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Christoph Hellwig Cc: Jeff Moyer , Ian Kent , Trond Myklebust , Ram Pai , autofs mailing list , linux-fsdevel Christoph Hellwig wrote: > To rephrease the above: With current mainline the nameidata argument > is always valid when ->lookup or ->d_revalidate are called except when > the filesystem uses lookup_one_len. lookup_one_len is a helper for fileystem > usage that is only valid to be used on the filesystems own trees. > Is this documented anywhere? How is one to know about this restriction since it isn't obvious from the code? And if this function is only to be used to lookup in ones own filesystem how is a filesystem supposed to lookup a file in another filesystem if they already have a directory dentry in hand? Walking up the dentry tree to recreate a path name so you can call path_walk seems a bit much. Without this capablility how does one write a stackable file system? Will