nfsd4: fix crash on unknown operation number
authorJ. Bruce Fields <bfields@redhat.com>
Wed, 22 Oct 2014 18:46:29 +0000 (14:46 -0400)
committerBen Hutchings <ben@decadent.org.uk>
Sun, 14 Dec 2014 16:23:50 +0000 (16:23 +0000)
commit758bcfbbe07b5afed0d62be4015ed73a165455b8
tree21297ffed73a0536507a23136891e021aa0e51e2
parentb4e59eddd5b2ceb8f45e7f5203e36dac447c4805
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: Ben Hutchings <ben@decadent.org.uk>
fs/nfsd/nfs4proc.c