nfsd4: fix crash on unknown operation number
authorJ. Bruce Fields <bfields@redhat.com>
Wed, 22 Oct 2014 18:46:29 +0000 (14:46 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Thu, 23 Oct 2014 17:39:51 +0000 (13:39 -0400)
commit51904b08072a8bf2b9ed74d1bd7a5300a614471d
tree13b33ba3eaa53d81fd8090d36d57fc85be330e10
parentd1d84c9626bb3a519863b3ffc40d347166f9fb83
nfsd4: fix crash on unknown operation number

Unknown operation numbers are caught in nfsd4_decode_compound() which
sets op->opnum to OP_ILLEGAL and op->status to nfserr_op_illegal.  The
error causes the main loop in nfsd4_proc_compound() to skip most
processing.  But nfsd4_proc_compound also peeks ahead at the next
operation in one case and doesn't take similar precautions there.

Cc: stable@vger.kernel.org
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4proc.c