> RFC 7530 permits COMMIT to return NFS4ERR_INVAL, but RFC 5661 and later do > not. Allow INVAL as a legacy behavior, but test for OK also. Do we have a 4.1 test to verify 4.1 and later doesn't return INVAL? Frank > Signed-off-by: Chuck Lever <chuck.lever@xxxxxxxxxx> > --- > nfs4.0/servertests/st_commit.py | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/nfs4.0/servertests/st_commit.py b/nfs4.0/servertests/st_commit.py > index 12a0dffa061f..4ef87e69c5d7 100644 > --- a/nfs4.0/servertests/st_commit.py > +++ b/nfs4.0/servertests/st_commit.py > @@ -160,4 +160,4 @@ def testCommitOverflow(t, env): > res = c.write_file(fh, _text, 0, stateid, how=UNSTABLE4) > check(res, msg="WRITE with how=UNSTABLE4") > res = c.commit_file(fh, 0xfffffffffffffff0, 64) > - check(res, NFS4ERR_INVAL, "COMMIT with offset + count overflow") > + check(res, [NFS4_OK, NFS4ERR_INVAL], "COMMIT with offset + count > + overflow")
