[PATCH 0/5] Dynamic Pseudo Root
Trond Myklebust
trond.myklebust at fys.uio.no
Mon Feb 18 15:12:57 EST 2008
On Mon, 2008-02-18 at 14:50 -0500, J. Bruce Fields wrote:
> On Mon, Feb 18, 2008 at 08:41:37PM +0100, Gabriel Barazer wrote:
> > On 02/18/2008 7:58:36 PM +0100, Trond Myklebust
> > <trond.myklebust at fys.uio.no> wrote:
> ...
> > >
> > > For instance, currently with NFSv3, I can have rules like
> > >
> > > /foo/bar client1
> > > /foo/bar/baz client1, client2
> > >
> > > How can you encode this topology if you want the pseudo-fs to be a
> > > separate filesystem? You'd have to have 2 different namespaces, one for
> > > client1, and one for client2.
> ...
> > About your example:
> > pseudoroot fs contains /foo/bar only (as /foo/bar/baz is a subdirectory
> > of /foo/bar, it is supposed to already physically exist). client1 see
> > its authorized exports, as well as client2 will see /foo/bar, but will
> > only be allowed to mount /foo/bar/baz.
>
> So if client2 does a readdir on /foo/bar, what does it see?
The READDIR call from client2 should normally just see the one entry
'baz' (and will generate the entries '.' and '..').
However if client1 calls READDIR, it should be allowed to see the entire
directory contents.
Trond
More information about the NFSv4
mailing list