From: Doug Ledford <dledford@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Steve Wise <swise@opengridcomputing.com>,
linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH RESEND] svcrdma: handle rdma read with a non-zero initial page offset
Date: Wed, 7 Oct 2015 13:33:05 -0400 [thread overview]
Message-ID: <56155751.7010903@redhat.com> (raw)
In-Reply-To: <20151007170151.GB26514@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 3117 bytes --]
On 10/07/2015 01:01 PM, J. Bruce Fields wrote:
> On Tue, Oct 06, 2015 at 01:44:25PM -0400, Doug Ledford wrote:
>> On 09/28/2015 05:46 PM, Steve Wise wrote:
>>> The server rdma_read_chunk_lcl() and rdma_read_chunk_frmr() functions
>>> were not taking into account the initial page_offset when determining
>>> the rdma read length. This resulted in a read who's starting address
>>> and length exceeded the base/bounds of the frmr.
>>>
>>> Most work loads don't tickle this bug apparently, but one test hit it
>>> every time: building the linux kernel on a 16 core node with 'make -j
>>> 16 O=/mnt/0' where /mnt/0 is a ramdisk mounted via NFSRDMA.
>>>
>>> This bug seems to only be tripped with devices having small fastreg page
>>> list depths. I didn't see it with mlx4, for instance.
>>
>> Bruce, what's you're take on this? Do you want to push this through or
>> would you care if I push it through my tree?
>
> Whoops, sorry, I meant to send a pull request for that last week. Uh, I
> think I'll go ahead and do that now if it's OK with you.
Fine with me. I was just trying to make sure it didn't get forgotten ;-)
> --b.
>
>>
>>> Fixes: 0bf4828983df ('svcrdma: refactor marshalling logic')
>>> Signed-off-by: Steve Wise <swise@opengridcomputing.com>
>>> Tested-by: Chuck Lever <chuck.lever@oracle.com>
>>> ---
>>>
>>> net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 6 ++++--
>>> 1 files changed, 4 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c b/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c
>>> index cb51742..5f6ca47 100644
>>> --- a/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c
>>> +++ b/net/sunrpc/xprtrdma/svc_rdma_recvfrom.c
>>> @@ -136,7 +136,8 @@ int rdma_read_chunk_lcl(struct svcxprt_rdma *xprt,
>>> ctxt->direction = DMA_FROM_DEVICE;
>>> ctxt->read_hdr = head;
>>> pages_needed = min_t(int, pages_needed, xprt->sc_max_sge_rd);
>>> - read = min_t(int, pages_needed << PAGE_SHIFT, rs_length);
>>> + read = min_t(int, (pages_needed << PAGE_SHIFT) - *page_offset,
>>> + rs_length);
>>>
>>> for (pno = 0; pno < pages_needed; pno++) {
>>> int len = min_t(int, rs_length, PAGE_SIZE - pg_off);
>>> @@ -235,7 +236,8 @@ int rdma_read_chunk_frmr(struct svcxprt_rdma *xprt,
>>> ctxt->direction = DMA_FROM_DEVICE;
>>> ctxt->frmr = frmr;
>>> pages_needed = min_t(int, pages_needed, xprt->sc_frmr_pg_list_len);
>>> - read = min_t(int, pages_needed << PAGE_SHIFT, rs_length);
>>> + read = min_t(int, (pages_needed << PAGE_SHIFT) - *page_offset,
>>> + rs_length);
>>>
>>> frmr->kva = page_address(rqstp->rq_arg.pages[pg_no]);
>>> frmr->direction = DMA_FROM_DEVICE;
>>>
>>> --
>>> 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
>>>
>>
>>
>> --
>> Doug Ledford <dledford@redhat.com>
>> GPG KeyID: 0E572FDD
>>
>>
>
>
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2015-10-07 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 21:46 [PATCH RESEND] svcrdma: handle rdma read with a non-zero initial page offset Steve Wise
2015-10-06 17:44 ` Doug Ledford
2015-10-07 17:01 ` J. Bruce Fields
2015-10-07 17:33 ` Doug Ledford [this message]
2015-10-07 20:41 ` 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=56155751.7010903@redhat.com \
--to=dledford@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@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).