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, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH] NFSD: Fix callback decoder status codes
Date: Mon, 10 Feb 2025 12:23:07 -0500	[thread overview]
Message-ID: <099cb10ef3399d7ebb9179eb3a6415562d409077.camel@kernel.org> (raw)
In-Reply-To: <20250210170332.115051-1-cel@kernel.org>

On Mon, 2025-02-10 at 12:03 -0500, cel@kernel.org wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
> 
> fs/nfsd/nfs4callback.c implements a callback client. Thus its XDR
> decoders are decoding replies, not calls.
> 
> NFS4ERR_BAD_XDR is an on-the-wire status code that reports that the
> client sent a corrupted RPC /call/. It's not used as the internal
> error code when a /reply/ can't be decoded, since that kind of
> failure is never reported to the sender of that RPC message.
> 
> Instead, a reply decoder should return -EIO, as the reply decoders
> in the NFS client do.
> 
> Fixes: 6487a13b5c6b ("NFSD: add support for CB_GETATTR callback")
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>  fs/nfsd/nfs4callback.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> This is only compile-tested, but I'm thinking of throwing this on
> the "for v6.15" pile.
> 
> 
> diff --git a/fs/nfsd/nfs4callback.c b/fs/nfsd/nfs4callback.c
> index 961b1defcb1a..ae4b7b6df47f 100644
> --- a/fs/nfsd/nfs4callback.c
> +++ b/fs/nfsd/nfs4callback.c
> @@ -101,15 +101,15 @@ static int decode_cb_fattr4(struct xdr_stream *xdr, uint32_t *bitmap,
>  
>  	if (bitmap[0] & FATTR4_WORD0_CHANGE)
>  		if (xdr_stream_decode_u64(xdr, &fattr->ncf_cb_change) < 0)
> -			return -NFSERR_BAD_XDR;
> +			return -EIO;
>  	if (bitmap[0] & FATTR4_WORD0_SIZE)
>  		if (xdr_stream_decode_u64(xdr, &fattr->ncf_cb_fsize) < 0)
> -			return -NFSERR_BAD_XDR;
> +			return -EIO;
>  	if (bitmap[2] & FATTR4_WORD2_TIME_DELEG_ACCESS) {
>  		fattr4_time_deleg_access access;
>  
>  		if (!xdrgen_decode_fattr4_time_deleg_access(xdr, &access))
> -			return -NFSERR_BAD_XDR;
> +			return -EIO;
>  		fattr->ncf_cb_atime.tv_sec = access.seconds;
>  		fattr->ncf_cb_atime.tv_nsec = access.nseconds;
>  
> @@ -118,7 +118,7 @@ static int decode_cb_fattr4(struct xdr_stream *xdr, uint32_t *bitmap,
>  		fattr4_time_deleg_modify modify;
>  
>  		if (!xdrgen_decode_fattr4_time_deleg_modify(xdr, &modify))
> -			return -NFSERR_BAD_XDR;
> +			return -EIO;
>  		fattr->ncf_cb_mtime.tv_sec = modify.seconds;
>  		fattr->ncf_cb_mtime.tv_nsec = modify.nseconds;
>  
> @@ -682,15 +682,15 @@ static int nfs4_xdr_dec_cb_getattr(struct rpc_rqst *rqstp,
>  	if (unlikely(status || cb->cb_status))
>  		return status;
>  	if (xdr_stream_decode_uint32_array(xdr, bitmap, 3) < 0)
> -		return -NFSERR_BAD_XDR;
> +		return -EIO;
>  	if (xdr_stream_decode_u32(xdr, &attrlen) < 0)
> -		return -NFSERR_BAD_XDR;
> +		return -EIO;
>  	maxlen = sizeof(ncf->ncf_cb_change) + sizeof(ncf->ncf_cb_fsize);
>  	if (bitmap[2] != 0)
>  		maxlen += (sizeof(ncf->ncf_cb_mtime.tv_sec) +
>  			   sizeof(ncf->ncf_cb_mtime.tv_nsec)) * 2;
>  	if (attrlen > maxlen)
> -		return -NFSERR_BAD_XDR;
> +		return -EIO;
>  	status = decode_cb_fattr4(xdr, bitmap, ncf);
>  	return status;
>  }

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

      reply	other threads:[~2025-02-10 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 17:03 [PATCH] NFSD: Fix callback decoder status codes cel
2025-02-10 17: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=099cb10ef3399d7ebb9179eb3a6415562d409077.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --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