linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] xprtrdma: rpcrdma_bc_receive_call() should init rq_private_buf.len
Date: Wed, 17 Feb 2016 10:25:54 -0500	[thread overview]
Message-ID: <56C49102.40304@Netapp.com> (raw)
In-Reply-To: <FDCF275D-FCBE-4A5B-A6F7-1FCF6618C2B7@oracle.com>

On 02/17/2016 10:19 AM, Chuck Lever wrote:
> 
>> On Feb 17, 2016, at 10:16 AM, Anna Schumaker <Anna.Schumaker@netapp.com> wrote:
>>
>> Hi Chuck,
>>
>> On 02/15/2016 10:23 AM, Chuck Lever wrote:
>>> Some NFSv4.1 OPEN requests were hanging waiting for the NFS server
>>> to finish recalling delegations. Turns out that each NFSv4.1 CB
>>> request on RDMA gets a GARBAGE_ARGS reply from the Linux client.
>>>
>>> Commit 756b9b37cfb2e3dc added a line in bc_svc_process that
>>> overwrites the incoming rq_rcv_buf's length with the value in
>>> rq_private_buf.len. But rpcrdma_bc_receive_call() does not invoke
>>> xprt_complete_bc_request(), thus rq_private_buf.len is not
>>> initialized. svc_process_common() is invoked with a zero-length
>>> RPC message, and fails.
>>>
>>> Fixes: 756b9b37cfb2e3dc ('SUNRPC: Fix callback channel')
>>> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
>>> ---
>>> Hi Anna-
>>>
>>> Commit 756b9b37cfb2e3dc in v4.5-rc1 introduced a behavior
>>> regression for NFSv4.1-over-RDMA. Would it be possible to merge
>>> this bug fix into 4.5-rc ?
>>>
>>>
>>> net/sunrpc/xprtrdma/backchannel.c |    2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/net/sunrpc/xprtrdma/backchannel.c b/net/sunrpc/xprtrdma/backchannel.c
>>> index cc1251d..2dcd764 100644
>>> --- a/net/sunrpc/xprtrdma/backchannel.c
>>> +++ b/net/sunrpc/xprtrdma/backchannel.c
>>> @@ -341,6 +341,8 @@ void rpcrdma_bc_receive_call(struct rpcrdma_xprt *r_xprt,
>>> 	rqst->rq_reply_bytes_recvd = 0;
>>> 	rqst->rq_bytes_sent = 0;
>>> 	rqst->rq_xid = headerp->rm_xid;
>>> +
>>
>> nit: Any reason for the extra newline?
> 
> Yes: xprt_complete_bc_request sets the private buffer length
> and sets RPC_BC_PA_IN_USE. So I want to group these two
> lines in their own paragraph just to "document" that they
> belong together and are not related to the lines above
> them.

Makes sense.  Thanks!

Anna

> 
> 
>>> +	rqst->rq_private_buf.len = size;
>>
>> This patch looks okay to me, and I'll make sure it's included in the next rc pull request Trond sends.
> 
> Thanks!
> 
> 
>> Thanks,
>> Anna
>>
>>> 	set_bit(RPC_BC_PA_IN_USE, &rqst->rq_bc_pa_state);
>>>
>>> 	buf = &rqst->rq_rcv_buf;
> 
> --
> Chuck Lever
> 
> 
> 
> 


      reply	other threads:[~2016-02-17 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 15:23 [PATCH] xprtrdma: rpcrdma_bc_receive_call() should init rq_private_buf.len Chuck Lever
2016-02-17 15:16 ` Anna Schumaker
2016-02-17 15:19   ` Chuck Lever
2016-02-17 15:25     ` Anna Schumaker [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=56C49102.40304@Netapp.com \
    --to=anna.schumaker@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@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).