NFS: define and initialize compound_hdr.replen
authorBenny Halevy <bhalevy@panasas.com>
Wed, 1 Apr 2009 13:22:07 +0000 (09:22 -0400)
committerBenny Halevy <bhalevy@panasas.com>
Wed, 17 Jun 2009 17:46:32 +0000 (10:46 -0700)
commit0c4e8c187758258ec58842384fe6a99cf1ce16c7
tree8b7018bc68b2cb0c2273ca58b986817a3ad9a5e4
parent6ce183919b4a09289cb0fe4fce960a9faa1e7c6b
NFS: define and initialize compound_hdr.replen

replen holds the running count of expected reply bytes.
repl will then be used by encoding routines for xdr_inline_pages offset
after which data bytes are to be received directly into the xdr
buffer pages.

NOTE: According to the nfsv4 and v4.1 RFCs, the replied tag SHOULD be the same
is the one sent, but this is not required as a MUST for the server to do so.
The server may screw us if it replies a tag of a different length in the
compound result.

[NFS: cb_compoundhdr.replen is in words not bytes]
Signed-off-by: Benny Halevy <bhalevy@panasas.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/nfs4xdr.c