Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: [PATCH v2 05/10] svcrdma: Find rmsgp more reliably
Date: Tue, 13 Jan 2015 11:03:11 -0500	[thread overview]
Message-ID: <20150113160311.8118.87208.stgit@klimt.1015granger.net> (raw)
In-Reply-To: <20150113155904.8118.57718.stgit@klimt.1015granger.net>

xdr_start() can return the wrong rmsgp address if an assumption
about how the xdr_buf was constructed changes.  When it gets it
wrong, the client receives a reply that has gibberish in the
RPC/RDMA header, preventing it from matching a waiting RPC request.

Instead, make (and document) just one assumption: that the RDMA
header for the client's RPC call is at the start of the first page
in rq_pages.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---

 net/sunrpc/xprtrdma/svc_rdma_sendto.c |   18 ++++--------------
 1 files changed, 4 insertions(+), 14 deletions(-)

diff --git a/net/sunrpc/xprtrdma/svc_rdma_sendto.c b/net/sunrpc/xprtrdma/svc_rdma_sendto.c
index 7d79897..7de33d1 100644
--- a/net/sunrpc/xprtrdma/svc_rdma_sendto.c
+++ b/net/sunrpc/xprtrdma/svc_rdma_sendto.c
@@ -483,18 +483,6 @@ void svc_rdma_prep_reply_hdr(struct svc_rqst *rqstp)
 {
 }
 
-/*
- * Return the start of an xdr buffer.
- */
-static void *xdr_start(struct xdr_buf *xdr)
-{
-	return xdr->head[0].iov_base -
-		(xdr->len -
-		 xdr->page_len -
-		 xdr->tail[0].iov_len -
-		 xdr->head[0].iov_len);
-}
-
 int svc_rdma_sendto(struct svc_rqst *rqstp)
 {
 	struct svc_xprt *xprt = rqstp->rq_xprt;
@@ -512,8 +500,10 @@ int svc_rdma_sendto(struct svc_rqst *rqstp)
 
 	dprintk("svcrdma: sending response for rqstp=%p\n", rqstp);
 
-	/* Get the RDMA request header. */
-	rdma_argp = xdr_start(&rqstp->rq_arg);
+	/* Get the RDMA request header. The receive logic always
+	 * places this at the start of page 0.
+	 */
+	rdma_argp = page_address(rqstp->rq_pages[0]);
 
 	/* Build an req vec for the XDR */
 	ctxt = svc_rdma_get_context(rdma);


  parent reply	other threads:[~2015-01-13 16:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 16:02 [PATCH v2 00/10] NFS/RDMA server for 3.20 Chuck Lever
2015-01-13 16:02 ` [PATCH v2 01/10] svcrdma: Clean up dprintk Chuck Lever
2015-01-13 16:02 ` [PATCH v2 02/10] svcrdma: Remove unused variable Chuck Lever
2015-01-13 16:02 ` [PATCH v2 03/10] svcrdma: Clean up read chunk counting Chuck Lever
2015-01-13 16:03 ` [PATCH v2 04/10] svcrdma: Scrub BUG_ON() and WARN_ON() call sites Chuck Lever
2015-01-13 16:03 ` Chuck Lever [this message]
2015-01-13 16:03 ` [PATCH v2 06/10] svcrdma: Plant reader function in struct svcxprt_rdma Chuck Lever
2015-01-13 16:03 ` [PATCH v2 07/10] svcrdma: rc_position sanity checking Chuck Lever
2015-01-13 16:03 ` [PATCH v2 08/10] svcrdma: Support RDMA_NOMSG requests Chuck Lever
2015-01-13 16:03 ` [PATCH v2 09/10] svcrdma: Move read list XDR round-up logic Chuck Lever
2015-01-13 16:03 ` [PATCH v2 10/10] svcrdma: Handle additional inline content Chuck Lever
2015-01-13 17:31 ` [PATCH v2 00/10] NFS/RDMA server for 3.20 Steve Wise
2015-01-15 19:01   ` J. Bruce Fields

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=20150113160311.8118.87208.stgit@klimt.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=bfields@fieldses.org \
    --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