NFSv4.1: keep seq_res.sr_slot as pointer rather than an index
authorBenny Halevy <bhalevy@panasas.com>
Fri, 24 Sep 2010 13:17:01 +0000 (09:17 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Fri, 24 Sep 2010 13:17:01 +0000 (09:17 -0400)
commitdfb4f309830359352539919f23accc59a20a3758
treec692dbb873e212bd919e6b98dac62478cb9ba968
parent7c563cc9f3f4aca70c27bd08a135499227f67014
NFSv4.1: keep seq_res.sr_slot as pointer rather than an index

Having to explicitly initialize sr_slotid to NFS4_MAX_SLOT_TABLE
resulted in numerous bugs.  Keeping the current slot as a pointer
to the slot table is more straight forward and robust as it's
implicitly set up to NULL wherever the seq_res member is initialized
to zeroes.

Signed-off-by: Benny Halevy <bhalevy@panasas.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/nfs4proc.c
fs/nfs/nfs4xdr.c
fs/nfs/read.c
fs/nfs/unlink.c
fs/nfs/write.c
include/linux/nfs_xdr.h