NFSv4: OPEN must handle the NFS4ERR_IO return code correctly
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Wed, 4 Dec 2013 22:39:23 +0000 (17:39 -0500)
committerBen Hutchings <ben@decadent.org.uk>
Tue, 1 Apr 2014 23:58:39 +0000 (00:58 +0100)
commit5144a343d0579973a631112decba5d0ced76e5c7
treef209ce1ebe6ca67aa74a2f1545079a67085cec47
parent2d6daf8d9db516be660c2e1646925c42eff942e0
NFSv4: OPEN must handle the NFS4ERR_IO return code correctly

commit c7848f69ec4a8c03732cde5c949bd2aa711a9f4b upstream.

decode_op_hdr() cannot distinguish between an XDR decoding error and
the perfectly valid errorcode NFS4ERR_IO. This is normally not a
problem, but for the particular case of OPEN, we need to be able
to increment the NFSv4 open sequence id when the server returns
a valid response.

Reported-by: J Bruce Fields <bfields@fieldses.org>
Link: http://lkml.kernel.org/r/20131204210356.GA19452@fieldses.org
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
fs/nfs/nfs4xdr.c