From: Chuck Lever <cel@kernel.org>
To: Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <cel@kernel.org>
Subject: [PATCH 2/2] nfsd: set op->status when an operation's header cannot be encoded
Date: Mon, 17 Aug 2026 20:57:15 -0400 [thread overview]
Message-ID: <20260817-jean-v1-2-9e356596ab85@kernel.org> (raw)
In-Reply-To: <20260817-jean-v1-0-9e356596ab85@kernel.org>
nfsd4_encode_operation() leaves op->status alone when the reply
buffer has no room for the operation's opcode and status word.
nfsd4_proc_compound() reads the unchanged nfs_ok as success and
goes on to the next operation, so the reply counts an operation
whose result was never encoded.
Report the failure through nfsd4_check_resp_size(), which the rest
of the function already uses. It returns NFS4ERR_REP_TOO_BIG, or
NFS4ERR_REP_TOO_BIG_TO_CACHE on a session, and the COMPOUND ends
at that operation.
Two paths narrow the reply buffer: nfsd4_sequence(), which rejects
a SEQUENCE result that does not fit, and nfsd4_encode_splice_read(),
which can leave a single XDR word in the head page. Whether a
COMPOUND reaches that boundary is unproven, so this is a guard
rather than a fix.
Signed-off-by: Chuck Lever <cel@kernel.org>
---
fs/nfsd/nfs4xdr.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
index 7d1b2d6f57f2..a154b02d82b3 100644
--- a/fs/nfsd/nfs4xdr.c
+++ b/fs/nfsd/nfs4xdr.c
@@ -6723,11 +6723,20 @@ nfsd4_encode_operation(struct nfsd4_compoundres *resp, struct nfsd4_op *op)
unsigned int op_status_offset;
nfsd4_enc encoder;
- if (xdr_stream_encode_u32(xdr, op->opnum) != XDR_UNIT)
+ /*
+ * nfsd4_proc_compound() stops the COMPOUND early only
+ * when op->status is set, so a header that cannot be
+ * encoded has to report the failure here.
+ */
+ if (xdr_stream_encode_u32(xdr, op->opnum) != XDR_UNIT) {
+ op->status = nfsd4_check_resp_size(resp, XDR_UNIT * 2);
goto release;
+ }
op_status_offset = xdr->buf->len;
- if (!xdr_reserve_space(xdr, XDR_UNIT))
+ if (!xdr_reserve_space(xdr, XDR_UNIT)) {
+ op->status = nfsd4_check_resp_size(resp, XDR_UNIT);
goto release;
+ }
if (op->opnum == OP_ILLEGAL)
goto status;
--
2.54.0
prev parent reply other threads:[~2026-08-18 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 0:57 [PATCH 0/2] nfsd: fix a slab overwrite in the NFSv4.1 session reply cache Chuck Lever
2026-08-18 0:57 ` [PATCH 1/2] nfsd: preflight SEQUENCE replies before accepting a slot Chuck Lever
2026-08-18 0:57 ` Chuck Lever [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260817-jean-v1-2-9e356596ab85@kernel.org \
--to=cel@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox