public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: cel@kernel.org, Neil Brown <neilb@suse.de>,
	Olga Kornievskaia	 <okorniev@redhat.com>,
	Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, Rick Macklem <rick.macklem@gmail.com>,
	 j.david.lists@gmail.com, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v4 0/9] Fix XDR encoding near page boundaries
Date: Thu, 02 Jan 2025 08:23:10 -0500	[thread overview]
Message-ID: <7f46e0fa59ec81795583e4ca2344f05b0f26fe99.camel@kernel.org> (raw)
In-Reply-To: <20241231002901.12725-1-cel@kernel.org>

On Mon, 2024-12-30 at 19:28 -0500, cel@kernel.org wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
> 
> Refresh the patch series to address the longstanding bug pointed out
> by J David and Rick Macklem.
> 
> Changes since v2:
> - Address same issue in NFSv4 READLINK and SECINFO operations
> - Update kdoc comment for xdr_reserve_space()
> 
> Chuck Lever (9):
>   NFSD: Encode COMPOUND operation status on page boundaries
>   NFSD: Insulate nfsd4_encode_read() from page boundaries in the encode
>     buffer
>   NFSD: Insulate nfsd4_encode_read_plus() from page boundaries in the
>     encode buffer
>   NFSD: Insulate nfsd4_encode_read_plus_data() from page boundaries in
>     the encode buffer
>   NFSD: Insulate nfsd4_encode_fattr4() from page boundaries in the
>     encode buffer
>   NFSD: Insulate nfsd4_encode_readlink() from page boundaries in the
>     encode buffer
>   NFSD: Refactor nfsd4_do_encode_secinfo() again
>   NFSD: Insulate nfsd4_encode_secinfo() from page boundaries in the
>     encode buffer
>   SUNRPC: Document validity guarantees of the pointer returned by
>     reserve_space
> 
>  fs/nfsd/nfs4xdr.c | 214 +++++++++++++++++++++++++---------------------
>  net/sunrpc/xdr.c  |   6 ++
>  2 files changed, 122 insertions(+), 98 deletions(-)
> 

Reviewed-by: Jeff Layton <jlayton@kernel.org>

      parent reply	other threads:[~2025-01-02 13:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-31  0:28 [PATCH v4 0/9] Fix XDR encoding near page boundaries cel
2024-12-31  0:28 ` [PATCH v4 1/9] NFSD: Encode COMPOUND operation status on " cel
2024-12-31  0:28 ` [PATCH v4 2/9] NFSD: Insulate nfsd4_encode_read() from page boundaries in the encode buffer cel
2024-12-31  0:28 ` [PATCH v4 3/9] NFSD: Insulate nfsd4_encode_read_plus() " cel
2024-12-31  0:28 ` [PATCH v4 4/9] NFSD: Insulate nfsd4_encode_read_plus_data() " cel
2024-12-31  0:28 ` [PATCH v4 5/9] NFSD: Insulate nfsd4_encode_fattr4() " cel
2024-12-31  0:28 ` [PATCH v4 6/9] NFSD: Insulate nfsd4_encode_readlink() " cel
2024-12-31  0:28 ` [PATCH v4 7/9] NFSD: Refactor nfsd4_do_encode_secinfo() again cel
2024-12-31  0:28 ` [PATCH v4 8/9] NFSD: Insulate nfsd4_encode_secinfo() from page boundaries in the encode buffer cel
2024-12-31  0:29 ` [PATCH v4 9/9] SUNRPC: Document validity guarantees of the pointer returned by reserve_space cel
2025-01-01 21:49   ` NeilBrown
2025-01-01 23:09     ` Chuck Lever
2025-01-02 13:21   ` Jeff Layton
2025-01-02 13: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=7f46e0fa59ec81795583e4ca2344f05b0f26fe99.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=j.david.lists@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=okorniev@redhat.com \
    --cc=rick.macklem@gmail.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