nfsd4: fix crash on unknown operation number
authorJ. Bruce Fields <bfields@redhat.com>
Wed, 22 Oct 2014 18:46:29 +0000 (14:46 -0400)
committerZefan Li <lizefan@huawei.com>
Mon, 2 Feb 2015 09:05:04 +0000 (17:05 +0800)
commit971918b8e4fbe202b6be1fa1a31f1991c08164dc
tree0aa76c613dd2668729bf356bc20976e34181c19b
parent6b91578a5af27dbba3c9b26bc918165eefcff7d3
nfsd4: fix crash on unknown operation number

commit 51904b08072a8bf2b9ed74d1bd7a5300a614471d upstream.

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.

Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Zefan Li <lizefan@huawei.com>
fs/nfsd/nfs4proc.c