Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 7/7] NFSD: Clean up nfs4svc_encode_compoundres()
Date: Mon, 29 Aug 2022 09:50:12 -0400	[thread overview]
Message-ID: <b64175263e298bc957c8dbf9c7cd2ee6ed84651c.camel@kernel.org> (raw)
In-Reply-To: <166171266025.21449.2692376100575745686.stgit@manet.1015granger.net>

On Sun, 2022-08-28 at 14:51 -0400, Chuck Lever wrote:
> In today's Linux NFS server implementation, the NFS dispatcher
> initializes each XDR result stream, and the NFSv4 .pc_func and
> .pc_encode methods all use xdr_stream-based encoding. This keeps
> rq_res.len automatically updated. There is no longer a need for
> the WARN_ON_ONCE() check in nfs4svc_encode_compoundres().
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>  fs/nfsd/nfs4xdr.c |    4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
> index 1e9690a061ec..af51e2a8ceb7 100644
> --- a/fs/nfsd/nfs4xdr.c
> +++ b/fs/nfsd/nfs4xdr.c
> @@ -5423,12 +5423,8 @@ bool
>  nfs4svc_encode_compoundres(struct svc_rqst *rqstp, struct xdr_stream *xdr)
>  {
>  	struct nfsd4_compoundres *resp = rqstp->rq_resp;
> -	struct xdr_buf *buf = xdr->buf;
>  	__be32 *p;
>  
> -	WARN_ON_ONCE(buf->len != buf->head[0].iov_len + buf->page_len +
> -				 buf->tail[0].iov_len);
> -
>  	/*
>  	 * Send buffer space for the following items is reserved
>  	 * at the top of nfsd4_proc_compound().
> 
> 

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

      reply	other threads:[~2022-08-29 13:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28 18:50 [PATCH v2 0/7] Fixes for server-side xdr_stream overhaul Chuck Lever
2022-08-28 18:50 ` [PATCH v2 1/7] SUNRPC: Fix svcxdr_init_decode's end-of-buffer calculation Chuck Lever
2022-08-29 12:48   ` Jeff Layton
2022-08-29 13:48     ` Chuck Lever III
2022-08-28 18:50 ` [PATCH v2 2/7] SUNRPC: Fix svcxdr_init_encode's buflen calculation Chuck Lever
2022-08-29 12:51   ` Jeff Layton
2022-08-28 18:50 ` [PATCH v2 3/7] NFSD: Protect against READDIR send buffer overflow Chuck Lever
2022-08-29 13:43   ` Jeff Layton
2022-08-29 13:59     ` Chuck Lever III
2022-08-28 18:50 ` [PATCH v2 4/7] NFSD: Use xdr_inline_decode() to decode NFSv3 symlinks Chuck Lever
2022-08-29 13:48   ` Jeff Layton
2022-08-28 18:50 ` [PATCH v2 5/7] NFSD: Clean up WRITE arg decoders Chuck Lever
2022-08-29 13:49   ` Jeff Layton
2022-08-28 18:50 ` [PATCH v2 6/7] SUNRPC: Fix typo in xdr_buf_subsegment's kdoc comment Chuck Lever
2022-08-29 13:49   ` Jeff Layton
2022-08-28 18:51 ` [PATCH v2 7/7] NFSD: Clean up nfs4svc_encode_compoundres() Chuck Lever
2022-08-29 13:50   ` 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=b64175263e298bc957c8dbf9c7cd2ee6ed84651c.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@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