Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: Mike Snitzer <snitzer@kernel.org>
Cc: neil@brown.name, jlayton@kernel.org, okorniev@redhat.com,
	dai.ngo@oracle.com, tom@talpey.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2] NFSD: Add array bounds-checking in nfsd_iter_read()
Date: Tue, 16 Sep 2025 09:03:45 -0700	[thread overview]
Message-ID: <ec014c3d-1182-4d47-b10d-b67da5623dcb@kernel.org> (raw)
In-Reply-To: <aMmJ31N8QKqw-YsT@kernel.org>

On 9/16/25 9:01 AM, Mike Snitzer wrote:
> On Tue, Sep 16, 2025 at 11:24:19AM -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>
> 
> Looks even better.

If Neil agrees, I will fold a similar change into the direct read
patch.


> Reviewed-by: Mike Snitzer <snitzer@kernel.org>
> 
> 
>> ---
>>  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);
>>  }
>>
>>
>>


-- 
Chuck Lever

  reply	other threads:[~2025-09-16 16:03 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 [this message]
2025-09-17  2:33 ` NeilBrown
2025-09-17 12:25 ` Jeff Layton

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=ec014c3d-1182-4d47-b10d-b67da5623dcb@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=snitzer@kernel.org \
    --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