> " " == Neil Brown <[EMAIL PROTECTED]> writes:
> - cannot do ".." lookups efficiently, or doesn't want to and
> - can protect against this sort of loop (and any other issues
>that
> the VFS usually protects against) itself
> then it can (with my patch) simpl
Hi,
On Tue, 20 Feb 2001, Trond Myklebust wrote:
> If I read the code correctly, we set the dentry d_flag
> DCACHE_NFSD_DISCONNECTED on such dummy dentries. We only force a
> lookup of the full path if the inode represents a directory or the
> NFSEXP_NOSUBTREECHECK export flag is not set.
IMO y
> " " == Roman Zippel <[EMAIL PROTECTED]> writes:
> If I read the source correctly, namespace operation are done
> with dir file handle + file name. I'm playing with the idea if
> we could relax the rule, that all dentries must be connected to
> the root. Inode to dentry l
Hi,
On 20 Feb 2001, Trond Myklebust wrote:
> 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.
If I read the source correctly, namespace operation are done with dir file
handle + file
> " " == Roman Zippel <[EMAIL PROTECTED]> 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
5 matches
Mail list logo