From: Jeff Layton <jlayton@kernel.org>
To: Aldo Ariel Panzardo <qwe.aldo@gmail.com>,
Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] nfsd: use xdr_encode_opaque_fixed for all GETXATTR fragments
Date: Tue, 15 Sep 2026 15:23:40 -0400 [thread overview]
Message-ID: <4bc95fa04f46b65a6ac6c494f008426571b7b873.camel@kernel.org> (raw)
In-Reply-To: <20260915173902.3184534-1-qwe.aldo@gmail.com>
On Tue, 2026-09-15 at 14:39 -0300, Aldo Ariel Panzardo wrote:
> nfsd4_vbuf_to_stream() already uses xdr_encode_opaque_fixed() when the
> final fragment is shorter than a page, but the preceding memcpy() in the
> loop body does not clear XDR padding.
>
> When the last fragment happens to be exactly PAGE_SIZE the short-fragment
> branch is never entered, and the loop exits through the normal buflen
> path. If that final page-sized reservation is not word-aligned within
> the XDR stream, its padding bytes are left stale.
>
> Convert the loop memcpy to xdr_encode_opaque_fixed() and drop the now
> redundant short-fragment padding block, matching the first-fragment fix.
>
> Suggested-by: Jeff Layton <jlayton@kernel.org>
> Cc: stable@vger.kernel.org
> Signed-off-by: Aldo Ariel Panzardo <qwe.aldo@gmail.com>
> ---
> fs/nfsd/nfs4xdr.c | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
> index XXXXXXX..XXXXXXX 100644
> --- a/fs/nfsd/nfs4xdr.c
> +++ b/fs/nfsd/nfs4xdr.c
> @@ -5963,15 +5963,7 @@ nfsd4_vbuf_to_stream(struct xdr_stream *xdr, char *buf, u32 buflen)
> if (!p)
> return nfserr_resource;
>
> - memcpy(p, buf, cplen);
> -
> - if (cplen < PAGE_SIZE) {
> - /*
> - * We're done, with a length that wasn't page
> - * aligned, so possibly not word aligned. Pad
> - * any trailing bytes with 0.
> - */
> - xdr_encode_opaque_fixed(p, NULL, cplen);
> - break;
> - }
> + xdr_encode_opaque_fixed(p, buf, cplen);
> + if (cplen < PAGE_SIZE)
> + break;
>
> buflen -= PAGE_SIZE;
> buf += PAGE_SIZE;
>
> --
> 2.43.0
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2026-09-15 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 17:39 Aldo Ariel Panzardo
2026-09-15 19:08 ` Chuck Lever
2026-09-15 19:23 ` Jeff Layton [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=4bc95fa04f46b65a6ac6c494f008426571b7b873.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=qwe.aldo@gmail.com \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®