linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Tucker <tom@opengridcomputing.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Steve Wise <swise@opengridcomputing.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2.6.30] svcrdma: Fix dma map direction for rdma read	targets
Date: Thu, 09 Apr 2009 14:17:48 -0500	[thread overview]
Message-ID: <49DE49DC.4050805@opengridcomputing.com> (raw)
In-Reply-To: <20090409153224.GB32589@fieldses.org>

J. Bruce Fields wrote:
> On Fri, Apr 03, 2009 at 03:23:47PM -0500, Tom Tucker wrote:
>> Steve Wise wrote:
>>> The nfs server rdma transport was mapping rdma read target pages for
>>> TO_DEVICE instead of FROM_DEVICE.  This causes data corruption on non
>>> cache-coherent systems if frmrs are used.
>>>
>>> Signed-off-by: Steve Wise <swise@opengridcomputing.com>
>>> ---
>>>
>>>  net/sunrpc/xprtrdma/svc_rdma_recvfrom.c |    2 +-
>>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c b/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c
>>> index 629a287..42a6f9f 100644
>>> --- a/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c
>>> +++ b/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c
>>> @@ -265,7 +265,7 @@ static int fast_reg_read_chunks(struct svcxprt_rdma *xprt,
>>>  		frmr->page_list->page_list[page_no] =
>>>  			ib_dma_map_single(xprt->sc_cm_id->device,
>>>  					  page_address(rqstp->rq_arg.pages[page_no]),
>>> -					  PAGE_SIZE, DMA_TO_DEVICE);
>>> +					  PAGE_SIZE, DMA_FROM_DEVICE);
>> FWIW, this looks good to me.
> 
> Thanks; I'll add an acked-by if you don't object. 

Sure...

>... Should this go to
> stable as well?
> 

I think so because it's a bug and we've verified it fixes the data 
corruption issue and doesn't regress existing platforms.


> --b.
> 
>>>  		if (ib_dma_mapping_error(xprt->sc_cm_id->device,
>>>  					 frmr->page_list->page_list[page_no]))
>>>  			goto fatal_err;
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" 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:[~2009-04-09 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 20:18 [PATCH 2.6.30] svcrdma: Fix dma map direction for rdma read targets Steve Wise
     [not found] ` <20090403201824.18102.62915.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2009-04-03 20:23   ` Tom Tucker
2009-04-09 15:32     ` J. Bruce Fields
2009-04-09 19:17       ` Tom Tucker [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=49DE49DC.4050805@opengridcomputing.com \
    --to=tom@opengridcomputing.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=swise@opengridcomputing.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;
as well as URLs for NNTP newsgroup(s).