From: Peter Staubach <staubach@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: iisaman@citi.umich.edu, linux-nfs@vger.kernel.org
Subject: Re: [PATCH pynfs] Allow server to reject maximum commit offsets
Date: Tue, 09 Feb 2010 17:28:52 -0500 [thread overview]
Message-ID: <4B71E1A4.1070604@redhat.com> (raw)
In-Reply-To: <20100209201231.GC30951@fieldses.org>
J. Bruce Fields wrote:
> From: J. Bruce Fields <bfields@citi.umich.edu>
>
> These two tests insist that a server must accept commits with offset
> 2^64-1 and 2^64-2. I can find no justification in the spec for this
> requirement.
>
> The linux server was recently changed to reject (with INVAL) offsets
> over 2^63-1, which is the maximum that the vfs commit routine can
> accept. That behavior is consistent with the NFSv3 commit
> implementation and with the NFSv4 write implementation.
>
I guess that I am missing something. At least the NFSv3
COMMIT operation takes an unsigned 64 bit quantity. That
would seem to make the test correct, would it not?
ps
> The maximum offset allowed may vary depending on filesystem or server,
> so I think it's simplest just to delete these tests. (Alternatively, we
> could replace the offset by whatever we consider a reasonable least
> common denominator, e.g. 2^31-1.)
>
> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
> ---
> lib/nfs4/servertests/st_commit.py | 18 ------------------
> 1 files changed, 0 insertions(+), 18 deletions(-)
>
> diff --git a/lib/nfs4/servertests/st_commit.py b/lib/nfs4/servertests/st_commit.py
> index 2955d79..0005e54 100644
> --- a/lib/nfs4/servertests/st_commit.py
> +++ b/lib/nfs4/servertests/st_commit.py
> @@ -35,24 +35,6 @@ def testCommitOffset1(t, env):
> """
> _commit(t, env.c1, 1)
>
> -def testCommitOffsetMax1(t, env):
> - """COMMIT
> -
> - FLAGS: commit all
> - DEPEND: MKFILE
> - CODE: CMT1c
> - """
> - _commit(t, env.c1, 0xffffffffffffffffL)
> -
> -def testCommitOffsetMax2(t, env):
> - """COMMIT
> -
> - FLAGS: commit all
> - DEPEND: MKFILE
> - CODE: CMT1d
> - """
> - _commit(t, env.c1, 0xfffffffffffffffeL)
> -
> def testCommitCount1(t, env):
> """COMMIT
>
next prev parent reply other threads:[~2010-02-09 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 20:12 [PATCH pynfs] Allow server to reject maximum commit offsets J. Bruce Fields
2010-02-09 20:13 ` J. Bruce Fields
2010-02-09 22:28 ` Peter Staubach [this message]
2010-02-09 22:42 ` J. Bruce Fields
2010-02-09 22:45 ` Peter Staubach
2010-02-09 22:50 ` J. Bruce Fields
2010-02-11 20:38 ` J. Bruce Fields
2010-02-11 21:32 ` Peter Staubach
2010-02-09 22:44 ` 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=4B71E1A4.1070604@redhat.com \
--to=staubach@redhat.com \
--cc=bfields@fieldses.org \
--cc=iisaman@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
/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