nfsd: fix corrupted reply to badly ordered compound

[ Upstream commit 5b7b15aee641904ae269be9846610a3950cbd64c ]

We're encoding a single op in the reply but leaving the number of ops
zero, so the reply makes no sense.

Somewhat academic as this isn't a case any real client will hit, though
in theory perhaps that could change in a future protocol extension.

Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
J. Bruce Fields 2018-06-13 15:21:35 -04:00 committed by Greg Kroah-Hartman
parent de6ccdbd77
commit a4f7bea878

View File

@ -1725,6 +1725,7 @@ nfsd4_proc_compound(struct svc_rqst *rqstp)
if (status) { if (status) {
op = &args->ops[0]; op = &args->ops[0];
op->status = status; op->status = status;
resp->opcnt = 1;
goto encode_op; goto encode_op;
} }