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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 13 Feb 2014 21:48:01 +0000 (13:48 -0800)
commitafce3609db524d801a8fc4096810fa6844062f65
treebaad405fa2d236e3a348d624e693776adf65b1cf
parent4371c272186d393fbb401a743867a209f3e218ae
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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/nfs/nfs4xdr.c