From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dax Kelson <dax@gurulabs.com>
Cc: "Kendrick M. Smith" <kmsmith@umich.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: Will NFSv4 be accepted?
Date: 15 Aug 2002 02:35:27 +0100 [thread overview]
Message-ID: <1029375327.28240.35.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0208141926030.31203-100000@mooru.gurulabs.com>
On Thu, 2002-08-15 at 02:27, Dax Kelson wrote:
> On 15 Aug 2002, Alan Cox wrote:
>
> > Thats not an NFS2 or NFS3 issue, thats an implementation matter. A
> > proper NFS credential system prevents that from occurring. You also have
> > to fix some bogon assumptions in our NFS client too I grant.
>
> Please, do tell.
Ok item #1 you authenticate with the server and get a cryptographic key
for use as credentials. This solves the bad client problem. Kerberos,
gssapi etc will do the job
Item #2 is a bug in our NFS page cache handling. Its not legal in NFS to
assume we can share caches between processes unless they have the same
NFS credentials for the query. The most we can do (and should do) is
that when we think we can reuse a cache entry we issue an NFS ACCESS
check for NFSv3 or for NFSv2 we write it back to the server if dirty
then issue a read for the new credential set.
next prev parent reply other threads:[~2002-08-15 1:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 23:01 patch 14/38: CLIENT: add ->setup_read() nfs_rpc_op for async read, part 1 Kendrick M. Smith
2002-08-14 20:49 ` Will NFSv4 be accepted? Dax Kelson
2002-08-14 22:17 ` Trond Myklebust
2002-08-14 22:34 ` [NFS] " Brian Pawlowski
2002-08-14 23:21 ` Alexander Viro
2002-08-15 1:10 ` Alan Cox
2002-08-15 6:18 ` marius aamodt eriksen
2002-08-15 11:08 ` Alan Cox
2002-08-15 6:23 ` marius aamodt eriksen
2002-08-15 14:19 ` Trond Myklebust
2002-08-15 1:09 ` Alan Cox
2002-08-15 1:27 ` Dax Kelson
2002-08-15 1:35 ` Alan Cox [this message]
2002-08-15 1:51 ` Dax Kelson
2002-08-15 4:07 ` J. Bruce Fields
2002-08-15 17:35 ` Linus Torvalds
2002-08-15 18:20 ` Dax Kelson
2002-08-15 19:52 ` Roger Luethi
2002-08-15 23:07 ` Trond Myklebust
2002-08-16 14:54 ` Oliver Xymoron
2002-08-16 19:44 ` Linus Torvalds
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=1029375327.28240.35.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dax@gurulabs.com \
--cc=kmsmith@umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®