Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 20 Feb 2001 04:44:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 20 Feb 2001 04:44:40 -0500 Received: from pat.uio.no ([129.240.130.16]:18838 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id ; Tue, 20 Feb 2001 04:44:36 -0500 To: Roman Zippel Cc: Neil Brown , Alan Cox , dek_ml@konerding.com, linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net, mason@suse.com Subject: Re: [NFS] Re: problems with reiserfs + nfs using 2.4.2-pre4 In-Reply-To: From: Trond Myklebust Content-Type: text/plain; charset=US-ASCII Date: 20 Feb 2001 10:44:07 +0100 In-Reply-To: Roman Zippel's message of "Tue, 20 Feb 2001 03:38:32 +0100 (MET)" Message-ID: Lines: 22 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >>>>> " " == Roman Zippel writes: > Hi, On Tue, 20 Feb 2001, Neil Brown wrote: >> 2/ lookup(".."). > A small question: Why exactly is this needed? Short answer: the existence of 'rename' makes it necessary, since it means that the directory path is volatile as far as the client is concerned. IIRC several NFS implementations (not Linux though) rely on being able to walk back up the directory tree in order to discover the path at any given moment. Under Linux, our reliance on dentries doesn't allow for directory paths to be volatile, so we don't support it. Instead we end up having to support aliased directories. Cheers, Trond - 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/