nfsd4: fix crash on unknown operation number
authorJ. Bruce Fields <bfields@redhat.com>
Wed, 22 Oct 2014 18:46:29 +0000 (14:46 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 14 Nov 2014 16:48:00 +0000 (08:48 -0800)
commitb51649f0c028f5cecd2bc55ee5b5901515f2ffc6
treef1d8c91daa09f4e402586836c8f40d53cab706e9
parent770600e703e72e27b66149550ea683b53b758b0c
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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/nfsd/nfs4proc.c