linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Devesh Sharma <devesh.sharma@broadcom.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-rdma@vger.kernel.org,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v1 06/10] svcrdma: Use correct XID in error replies
Date: Fri, 5 Feb 2016 16:11:06 +0530	[thread overview]
Message-ID: <CANjDDBjYB+Lk5VUd8eojkfxws_ZL_tqxcGKZbg=xV2MAMRuVWQ@mail.gmail.com> (raw)
In-Reply-To: <20160203155211.13868.35749.stgit@klimt.1015granger.net>

Looks good.

On Wed, Feb 3, 2016 at 9:22 PM, Chuck Lever <chuck.lever@oracle.com> wrote:
> When constructing an error reply, svc_rdma_xdr_encode_error()
> needs to view the client's request message so it can get the
> failing request's XID.
>
> svc_rdma_xdr_decode_req() is supposed to return a pointer to the
> client's request header. But if it fails to decode the client's
> message (and thus an error reply is needed) it does not return the
> pointer. The server then sends a bogus XID in the error reply.
>
> Instead, unconditionally generate the pointer to the client's header
> in svc_rdma_recvfrom(), and pass that pointer to both functions.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>  include/linux/sunrpc/svc_rdma.h         |    2 +-
>  net/sunrpc/xprtrdma/svc_rdma_marshal.c  |    7 +------
>  net/sunrpc/xprtrdma/svc_rdma_recvfrom.c |    3 ++-
>  3 files changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/include/linux/sunrpc/svc_rdma.h b/include/linux/sunrpc/svc_rdma.h
> index 0589918..4ce7b74 100644
> --- a/include/linux/sunrpc/svc_rdma.h
> +++ b/include/linux/sunrpc/svc_rdma.h
> @@ -199,7 +199,7 @@ extern int svc_rdma_handle_bc_reply(struct rpc_xprt *xprt,
>                                     struct xdr_buf *rcvbuf);
>
>  /* svc_rdma_marshal.c */
> -extern int svc_rdma_xdr_decode_req(struct rpcrdma_msg **, struct svc_rqst *);
> +extern int svc_rdma_xdr_decode_req(struct rpcrdma_msg *, struct svc_rqst *);
>  extern int svc_rdma_xdr_encode_error(struct svcxprt_rdma *,
>                                      struct rpcrdma_msg *,
>                                      enum rpcrdma_errcode, __be32 *);
> diff --git a/net/sunrpc/xprtrdma/svc_rdma_marshal.c b/net/sunrpc/xprtrdma/svc_rdma_marshal.c
> index e2fca76..c011b12 100644
> --- a/net/sunrpc/xprtrdma/svc_rdma_marshal.c
> +++ b/net/sunrpc/xprtrdma/svc_rdma_marshal.c
> @@ -145,15 +145,11 @@ static __be32 *decode_reply_array(__be32 *va, __be32 *vaend)
>         return (__be32 *)&ary->wc_array[nchunks];
>  }
>
> -int svc_rdma_xdr_decode_req(struct rpcrdma_msg **rdma_req,
> -                           struct svc_rqst *rqstp)
> +int svc_rdma_xdr_decode_req(struct rpcrdma_msg *rmsgp, struct svc_rqst *rqstp)
>  {
> -       struct rpcrdma_msg *rmsgp = NULL;
>         __be32 *va, *vaend;
>         u32 hdr_len;
>
> -       rmsgp = (struct rpcrdma_msg *)rqstp->rq_arg.head[0].iov_base;
> -
>         /* Verify that there's enough bytes for header + something */
>         if (rqstp->rq_arg.len <= RPCRDMA_HDRLEN_MIN) {
>                 dprintk("svcrdma: header too short = %d\n",
> @@ -201,7 +197,6 @@ int svc_rdma_xdr_decode_req(struct rpcrdma_msg **rdma_req,
>         hdr_len = (unsigned long)va - (unsigned long)rmsgp;
>         rqstp->rq_arg.head[0].iov_len -= hdr_len;
>
> -       *rdma_req = rmsgp;
>         return hdr_len;
>  }
>
> diff --git a/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c b/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c
> index 0f09052..8f68cb6 100644
> --- a/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c
> +++ b/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c
> @@ -653,7 +653,8 @@ int svc_rdma_recvfrom(struct svc_rqst *rqstp)
>         rdma_build_arg_xdr(rqstp, ctxt, ctxt->byte_len);
>
>         /* Decode the RDMA header. */
> -       ret = svc_rdma_xdr_decode_req(&rmsgp, rqstp);
> +       rmsgp = (struct rpcrdma_msg *)rqstp->rq_arg.head[0].iov_base;
> +       ret = svc_rdma_xdr_decode_req(rmsgp, rqstp);
>         if (ret < 0)
>                 goto out_err;
>         rqstp->rq_xprt_hlen = ret;
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-02-05 10:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 15:51 [PATCH v1 00/10] NFS/RDMA server patches for v4.6 Chuck Lever
2016-02-03 15:51 ` [PATCH v1 01/10] svcrdma: Do not send XDR roundup bytes for a write chunk Chuck Lever
2016-02-05 10:11   ` Devesh Sharma
2016-02-03 15:51 ` [PATCH v1 02/10] svcrdma: Make svc_rdma_get_frmr() not sleep Chuck Lever
2016-02-05 10:15   ` Devesh Sharma
2016-02-05 16:29     ` Chuck Lever
2016-02-05 17:49       ` Devesh Sharma
2016-02-05 18:13         ` Chuck Lever
2016-02-06 15:56           ` Devesh Sharma
2016-02-03 15:51 ` [PATCH v1 03/10] svcrdma: svc_rdma_post_recv() should close connection on error Chuck Lever
2016-02-05 10:17   ` Devesh Sharma
2016-02-03 15:51 ` [PATCH v1 04/10] rpcrdma: Add missing XDR union fields for RDMA errors Chuck Lever
2016-02-05 10:23   ` Devesh Sharma
2016-02-05 15:53     ` Chuck Lever
2016-02-03 15:52 ` [PATCH v1 05/10] svcrdma: Make RDMA_ERROR messages work Chuck Lever
2016-02-05 10:35   ` Devesh Sharma
2016-02-03 15:52 ` [PATCH v1 06/10] svcrdma: Use correct XID in error replies Chuck Lever
2016-02-05 10:41   ` Devesh Sharma [this message]
2016-02-03 15:52 ` [PATCH v1 07/10] svcrdma: Hook up the logic to return ERR_CHUNK Chuck Lever
2016-02-05 10:45   ` Devesh Sharma
2016-02-03 15:52 ` [PATCH v1 08/10] svcrdma: Remove close_out exit path Chuck Lever
2016-02-05 10:41   ` Devesh Sharma
2016-02-03 15:52 ` [PATCH v1 09/10] svcrdma: Use new CQ API for RPC-over-RDMA server receive CQs Chuck Lever
2016-02-05 10:51   ` Devesh Sharma
2016-02-03 15:52 ` [PATCH v1 10/10] svcrdma: Use new CQ API for RPC-over-RDMA server send CQs Chuck Lever
2016-02-05 10:56   ` Devesh Sharma
2016-02-05 10:59 ` [PATCH v1 00/10] NFS/RDMA server patches for v4.6 Devesh Sharma

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='CANjDDBjYB+Lk5VUd8eojkfxws_ZL_tqxcGKZbg=xV2MAMRuVWQ@mail.gmail.com' \
    --to=devesh.sharma@broadcom.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@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;
as well as URLs for NNTP newsgroup(s).