From: Steve Dickson <SteveD@RedHat.com>
To: nfs@lists.sourceforge.net
Subject: A Question about the 2.4.21 Pathconf patch
Date: Tue, 29 Apr 2003 11:08:30 -0400 [thread overview]
Message-ID: <3EAE956E.9080205@RedHat.com> (raw)
I noticed in the Trond's linux-2.4.21-08-pathconf.dif patch that
nfs_proc_fsinfo uses
the NFSPROC_STATFS instead of (what I would expect) the NFSPROC_FSINFO
procedure as defined in the v3 spec. Now I realize that fsinfo is not
support in v2
but doesn't it make sense to use it with v3 or am I missing something here.
I would think that if the server sent some numbers that the client
couldn't handle,
the client would simple fail the mount...
Has anybody tried using NFSPROC_FSINFO instead of NFSPROC_STATFS?
SteveD
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-04-29 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 15:08 Steve Dickson [this message]
2003-04-29 16:22 ` A Question about the 2.4.21 Pathconf patch Trond Myklebust
2003-04-29 18:41 ` Steve Dickson
2003-04-29 19:39 ` Trond Myklebust
2003-04-29 21:18 ` Steve Dickson
2003-04-29 22:47 ` Trond Myklebust
2003-04-30 2:14 ` Steve Dickson
2003-04-29 19:55 ` Trond Myklebust
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=3EAE956E.9080205@RedHat.com \
--to=steved@redhat.com \
--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