From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Roman Zippel <zippel@fh-brandenburg.de>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] Re: problems with reiserfs + nfs using 2.4.2-pre4
Date: 21 Feb 2001 13:43:08 +0100 [thread overview]
Message-ID: <shs4rxojjfn.fsf@charged.uio.no> (raw)
In-Reply-To: <14993.48376.203279.390285@notabene.cse.unsw.edu.au> <Pine.GSO.4.10.10102200330330.25095-100000@zeus.fh-brandenburg.de> <14995.12200.46230.717479@notabene.cse.unsw.edu.au>
In-Reply-To: Neil Brown's message of "Wed, 21 Feb 2001 14:02:00 +1100 (EST)"
>>>>> " " == Neil Brown <neilb@cse.unsw.edu.au> 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) simply define decode_fh and
> encode_fh and do whatever it likes, such as create a dentry
> that isn't properly connected.
Do we really want to design for this though?
Being able to look up the parent directory is explicitly encoded in
all revisions of the NFS protocol. In NFSv2/v3 the names '.' and '..'
have a clearly defined meaning, whereas in NFSv4 you are required to
support LOOKUPP.
I can't speculate about the needs of other networked filesystems which
may want to use this handle interface, but as far NFS is concerned we
are not interested in considering such special cases.
Cheers,
Trond
next prev parent reply other threads:[~2001-02-21 12:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 0:18 problems with reiserfs + nfs using 2.4.2-pre4 dek_ml
2001-02-19 0:37 ` Neil Brown
2001-02-19 2:56 ` dek_ml
2001-02-19 3:40 ` Neil Brown
2001-02-19 11:23 ` Alan Cox
2001-02-20 0:40 ` Neil Brown
2001-02-20 1:15 ` Chris Mason
2001-02-20 1:34 ` Neil Brown
2001-02-20 1:24 ` Alan Cox
2001-02-20 1:37 ` Neil Brown
2001-02-20 2:11 ` dek_ml
2001-02-20 22:54 ` Brian May
2001-02-20 23:30 ` Chris Mason
2001-02-20 2:38 ` Roman Zippel
2001-02-20 9:44 ` [NFS] " Trond Myklebust
2001-02-20 14:02 ` Roman Zippel
2001-02-20 15:16 ` Trond Myklebust
2001-02-20 16:26 ` Roman Zippel
2001-02-21 3:02 ` Neil Brown
2001-02-21 12:43 ` Trond Myklebust [this message]
2001-02-19 1:55 ` Alan Cox
2001-02-19 15:37 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=shs4rxojjfn.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=zippel@fh-brandenburg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox