From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>,
neil@brown.name, okorniev@redhat.com, dai.ngo@oracle.com,
tom@talpey.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2] NFSD: Add array bounds-checking in nfsd_iter_read()
Date: Wed, 17 Sep 2025 08:25:51 -0400 [thread overview]
Message-ID: <f2bc098001ae2346abc35817bd6bec46742b7140.camel@kernel.org> (raw)
In-Reply-To: <175803617610.13710.7007300747292684854.stgit@oracle-102.nfsv4bat.org>
On Tue, 2025-09-16 at 11:24 -0400, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> The *count parameter does not appear to be explicitly restricted
> to being smaller than rsize, so it might be possible to overrun
> the rq_bvec or rq_pages arrays.
>
> Rather than overrunning these arrays (damage done!) and then WARNING
> once, let's harden the loop so that it terminates before the end of
> the arrays are reached. This should result in a short read, which is
> OK -- clients recover by sending additional READ requests for the
> remaining unread bytes.
>
> Reported-by: NeilBrown <neil@brown.name>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> fs/nfsd/vfs.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> Changes since v1:
> - Check for overrunning rq_pages as well
> - Move bounds checking to top of the loop
> - Move incrementing to the bottom of the loop
>
> diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
> index 714777c221ed..2026431500ec 100644
> --- a/fs/nfsd/vfs.c
> +++ b/fs/nfsd/vfs.c
> @@ -1115,18 +1115,20 @@ __be32 nfsd_iter_read(struct svc_rqst *rqstp, struct svc_fh *fhp,
>
> v = 0;
> total = *count;
> - while (total) {
> + while (total && v < rqstp->rq_maxpages &&
> + rqstp->rq_next_page < rqstp->rq_page_end) {
> len = min_t(size_t, total, PAGE_SIZE - base);
> - bvec_set_page(&rqstp->rq_bvec[v], *(rqstp->rq_next_page++),
> + bvec_set_page(&rqstp->rq_bvec[v], *rqstp->rq_next_page,
> len, base);
> +
> total -= len;
> + ++rqstp->rq_next_page;
> ++v;
> base = 0;
> }
> - WARN_ON_ONCE(v > rqstp->rq_maxpages);
>
> - trace_nfsd_read_vector(rqstp, fhp, offset, *count);
> - iov_iter_bvec(&iter, ITER_DEST, rqstp->rq_bvec, v, *count);
> + trace_nfsd_read_vector(rqstp, fhp, offset, *count - total);
> + iov_iter_bvec(&iter, ITER_DEST, rqstp->rq_bvec, v, *count - total);
> host_err = vfs_iocb_iter_read(file, &kiocb, &iter);
> return nfsd_finish_read(rqstp, fhp, file, offset, count, eof, host_err);
> }
>
Much nicer.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2025-09-17 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 15:24 [PATCH v2] NFSD: Add array bounds-checking in nfsd_iter_read() Chuck Lever
2025-09-16 16:01 ` Mike Snitzer
2025-09-16 16:03 ` Chuck Lever
2025-09-17 2:33 ` NeilBrown
2025-09-17 12:25 ` 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=f2bc098001ae2346abc35817bd6bec46742b7140.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=dai.ngo@oracle.com \
--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