From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Kent <raven@themaw.net>
Subject: Re: [PATCH 0/7] Permit filesystem local caching and NFS superblock
	sharing [try #13]
Date: Wed, 06 Sep 2006 18:27:58 +0800
Message-ID: <1157538478.4050.0.camel@raven.themaw.net>
References: <1157421445.5510.13.camel@localhost>
	<20060901195009.187af603.akpm@osdl.org>
	<20060831102127.8fb9a24b.akpm@osdl.org>
	<20060830135503.98f57ff3.akpm@osdl.org>
	<20060830125239.6504d71a.akpm@osdl.org>
	<20060830193153.12446.24095.stgit@warthog.cambridge.redhat.com>
	<27414.1156970238@warthog.cambridge.redhat.com>
	<9849.1157018310@warthog.cambridge.redhat.com>
	<9534.1157116114@warthog.cambridge.redhat.com>
	<20060901093451.87aa486d.akpm@osdl.org>
	<1157130044.5632.87.camel@localhost>
	<28945.1157370732@warthog.cambridge.redhat.com>
	<1157376295.3240.13.camel@raven.themaw.net>
	<4012.1157450226@warthog.cambridge.redhat.com>
	<1157460472.5621.3.camel@localhost>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: Andrew Morton <akpm@osdl.org>, nfsv4@linux-nfs.org, steved@redhat.com,
	linux-kernel@vger.kernel.org,
	David Howells <dhowells@redhat.com>, torvalds@osdl.org,
	linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org
Return-path: <nfsv4-bounces@linux-nfs.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
In-Reply-To: <1157460472.5621.3.camel@localhost>
List-Unsubscribe: <http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4>,
	<mailto:nfsv4-request@linux-nfs.org?subject=unsubscribe>
List-Archive: <http://linux-nfs.org/pipermail/nfsv4>
List-Post: <mailto:nfsv4@linux-nfs.org>
List-Help: <mailto:nfsv4-request@linux-nfs.org?subject=help>
List-Subscribe: <http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4>,
	<mailto:nfsv4-request@linux-nfs.org?subject=subscribe>
Sender: nfsv4-bounces@linux-nfs.org
Errors-To: nfsv4-bounces@linux-nfs.org
List-Id: linux-fsdevel.vger.kernel.org

On Tue, 2006-09-05 at 08:47 -0400, Trond Myklebust wrote:
> On Tue, 2006-09-05 at 10:57 +0100, David Howells wrote:
> > Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> > 
> > > Why the hell is it doing a mkdir in the first place?
> > 
> > I think the problems it is solving are these:
> > 
> >  (1) What happens if "/" is _not_ exported?
> > 
> >  (2) What happens if some intermediate directory (say "/usr") is not
> >      accessible?
> > 
> > 
> > In the first case, the automounter just makes "usr" and "usr/src", say, in the
> > autofs filesystem, and then mounts server:/usr/src on that.
> 
> That is fine. As long as it is doing so in the _autofs_ filesystem. A
> call to 'stat()' should suffice to tell if this is the case.
> 
> > In the second case, the automounter relies on NFS letting it make intervening
> > directories it couldn't otherwise access to span the gap between "/" and
> > "src".
> 
> If the directory isn't accessible, then autofs shouldn't be trying to
> override that. It certainly shouldn't be doing so by trying to create
> the directory.
> 

In the case above the directory is in the autofs filesystem and so needs
to be created.

Ian