From: Peter Staubach <staubach@redhat.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Al Viro <viro@ftp.linux.org.uk>,
akpm@osdl.org, andros@citi.umich.edu, bfields@citi.umich.edu,
Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org, Neil Brown <neilb@suse.de>,
Olaf Kirch <okir@suse.de>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: NFS4 crack\
Date: Mon, 26 Sep 2005 13:13:53 -0400 [thread overview]
Message-ID: <43382C51.6000608@redhat.com> (raw)
In-Reply-To: <OF0DEBFDD3.4E946B90-ON88257088.0059E511-88257088.005AA2B4@us.ibm.com>
Bryan Henderson wrote:
>
>Well, I wouldn't want to. I can't think of anything that an NFS server
>does to a directory that couldn't be done cleanly with a single system
>call, much the way the POSIX system calls do.
>
I might object to the characterization of "cleanly". We would need system
calls which matched the specific semantics of NFS operations. For example,
we would need system calls which understood pre-operations and
post-operation
attributes. We would need system calls which understood 32 bit limits so
that we could correctly implement NFS version 2. NFS version 3 and NFS
version 2 are probably close enough that we could use a common set of
system calls with appropriate flags, but it does not seem likely that these
system calls would suffice for NFS version 4. We could end up with a whole
lot of system calls, even if they all went through a common entry point into
the kernel.
Thanx...
ps
next prev parent reply other threads:[~2005-09-26 17:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 10:21 NFS4 crack Christoph Hellwig
2005-09-18 14:36 ` J. Bruce Fields
2005-09-19 10:35 ` Christoph Hellwig
2005-09-19 13:04 ` Anton Altaparmakov
2005-09-19 13:35 ` J. Bruce Fields
2005-09-19 13:39 ` Christoph Hellwig
2005-09-19 14:07 ` J. Bruce Fields
2005-09-19 14:11 ` Christoph Hellwig
2005-09-19 17:13 ` Bryan Henderson
2005-09-19 17:16 ` Randy.Dunlap
2005-09-19 21:57 ` Bryan Henderson
2005-09-19 22:11 ` Randy.Dunlap
2005-09-20 0:17 ` Bryan Henderson
2005-09-19 18:02 ` Christoph Hellwig
2005-09-19 18:53 ` William A.(Andy) Adamson
2005-09-19 18:59 ` Christoph Hellwig
2005-09-19 22:04 ` Bryan Henderson
2005-09-19 19:01 ` J. Bruce Fields
2005-09-19 19:05 ` Christoph Hellwig
2005-09-19 20:31 ` J. Bruce Fields
2005-09-20 12:49 ` Greg KH
2005-09-20 15:10 ` William A.(Andy) Adamson
2005-09-20 18:37 ` Neil Brown
2005-09-21 7:44 ` Andrew Morton
2005-09-22 20:58 ` William A.(Andy) Adamson
2005-09-21 13:41 ` Trond Myklebust
2005-09-21 14:40 ` J. Bruce Fields
2005-09-22 16:28 ` Bryan Henderson
2005-09-22 16:52 ` Trond Myklebust
2005-09-22 17:38 ` Peter Staubach
2005-09-22 17:52 ` Trond Myklebust
2005-09-22 18:07 ` Peter Staubach
2005-09-22 21:08 ` Bryan Henderson
2005-09-23 12:17 ` Peter Staubach
2005-09-23 20:50 ` Bryan Henderson
2005-09-23 21:02 ` NFS4 crack\ Al Viro
2005-09-26 16:29 ` Bryan Henderson
2005-09-26 17:13 ` Peter Staubach [this message]
2005-09-22 21:48 ` NFS4 crack Nicholas Miell
2005-09-22 22:50 ` Greg Banks
2005-09-22 21:19 ` Bryan Henderson
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=43382C51.6000608@redhat.com \
--to=staubach@redhat.com \
--cc=akpm@osdl.org \
--cc=andros@citi.umich.edu \
--cc=bfields@citi.umich.edu \
--cc=hbryan@us.ibm.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okir@suse.de \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@ftp.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.