From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, linux-nfs@vger.kernel.org
Cc: viro@zeniv.linux.org.uk, dcritch@redhat.com, d.lesca@solinos.it
Subject: Re: [PATCH v1 0/3] rq_pages bounds checking
Date: Sat, 18 Mar 2023 06:04:01 -0400 [thread overview]
Message-ID: <cf2ad1349a19b472653c500cc7e287843a0cb8c7.camel@kernel.org> (raw)
In-Reply-To: <167909365790.1672.13118429954916842449.stgit@klimt.1015granger.net>
On Fri, 2023-03-17 at 19:01 -0400, Chuck Lever wrote:
> A slightly modified take on Jeff's earlier patches, tested with
> both NFSv3 and NFSv4.1 via simple fault injection in
> svc_rqst_replace_page().
>
> In general I'm in favor of more rq_pages bounds checking by
> replacing direct modification of the rq_respages and rq_next_page
> fields with accessor functions.
>
> ---
>
> Chuck Lever (2):
> SUNRPC: add bounds checking to svc_rqst_replace_page
> NFSD: Watch for rq_pages bounds checking errors in nfsd_splice_actor()
>
> Jeff Layton (1):
> nfsd: don't replace page in rq_pages if it's a continuation of last page
>
>
> fs/nfsd/vfs.c | 15 +++++++++++++--
> include/linux/sunrpc/svc.h | 2 +-
> include/trace/events/sunrpc.h | 25 +++++++++++++++++++++++++
> net/sunrpc/svc.c | 15 ++++++++++++++-
> 4 files changed, 53 insertions(+), 4 deletions(-)
>
> --
> Chuck Lever
>
Looks good, Chuck, thanks. You can add this to the last two:
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-03-18 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 23:01 [PATCH v1 0/3] rq_pages bounds checking Chuck Lever
2023-03-17 23:01 ` [PATCH v1 1/3] nfsd: don't replace page in rq_pages if it's a continuation of last page Chuck Lever
2023-03-17 23:01 ` [PATCH v1 2/3] SUNRPC: add bounds checking to svc_rqst_replace_page Chuck Lever
2023-03-17 23:01 ` [PATCH v1 3/3] NFSD: Watch for rq_pages bounds checking errors in nfsd_splice_actor() Chuck Lever
2023-03-18 10:04 ` Jeff Layton [this message]
2023-03-18 15:20 ` [PATCH v1 0/3] rq_pages bounds checking Chuck Lever III
2023-03-18 16:37 ` 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=cf2ad1349a19b472653c500cc7e287843a0cb8c7.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=d.lesca@solinos.it \
--cc=dcritch@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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