nfsd41: use session maxreqs for sequence target and highest slotid
authorAndy Adamson <andros@netapp.com>
Fri, 28 Aug 2009 12:45:02 +0000 (08:45 -0400)
committerJ. Bruce Fields <bfields@citi.umich.edu>
Wed, 2 Sep 2009 02:24:05 +0000 (22:24 -0400)
commita8dfdaeb7a8b1295f45d9d208dd27e6e20113d1b
treefd7bdabd4f66ee054fc2b2e2d6b39089d5a5b972
parenta649637c73a36174287a403cdda7607177d64523
nfsd41: use session maxreqs for sequence target and highest slotid

This fixes a bug in the sequence operation reply.

The sequence operation returns the highest slotid it will accept in the future
in sr_highest_slotid, and the highest slotid it prefers the client to use.
Since we do not re-negotiate the session slot table yet, these should both
always be set to the session ca_maxrequests.

Signed-off-by: Andy Adamson <andros@netapp.com>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
fs/nfsd/nfs4state.c