All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] SUNRPC: Ensure that call_bind times out correctly
Date: Tue, 18 Mar 2014 15:02:42 -0400	[thread overview]
Message-ID: <53289852.9050806@RedHat.com> (raw)
In-Reply-To: <1395081645-11906-2-git-send-email-trond.myklebust@primarydata.com>



On 03/17/2014 02:40 PM, Trond Myklebust wrote:
> If the rpcbind server is unavailable, we still want the RPC client
> to respect the timeout.
> 
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Tested-by: Steve Dickson <steved@redhat.com>

steved.

> ---
>  net/sunrpc/clnt.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
> index f22d3a115fda..53a13835b90f 100644
> --- a/net/sunrpc/clnt.c
> +++ b/net/sunrpc/clnt.c
> @@ -1728,9 +1728,7 @@ call_bind_status(struct rpc_task *task)
>  	case -EPROTONOSUPPORT:
>  		dprintk("RPC: %5u remote rpcbind version unavailable, retrying\n",
>  				task->tk_pid);
> -		task->tk_status = 0;
> -		task->tk_action = call_bind;
> -		return;
> +		goto retry_timeout;
>  	case -ECONNREFUSED:		/* connection problems */
>  	case -ECONNRESET:
>  	case -ECONNABORTED:
> @@ -1756,6 +1754,7 @@ call_bind_status(struct rpc_task *task)
>  	return;
>  
>  retry_timeout:
> +	task->tk_status = 0;
>  	task->tk_action = call_timeout;
>  }
>  
> 

  reply	other threads:[~2014-03-18 19:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 18:40 [PATCH 1/2] SUNRPC: Ensure that call_connect times out correctly Trond Myklebust
2014-03-17 18:40 ` [PATCH 2/2] SUNRPC: Ensure that call_bind " Trond Myklebust
2014-03-18 19:02   ` Steve Dickson [this message]
2014-03-18 15:47 ` [PATCH 1/2] SUNRPC: Ensure that call_connect " Steve Dickson
2014-03-18 15:58   ` Trond Myklebust
2014-03-18 17:24     ` Steve Dickson
2014-03-18 18:45       ` Trond Myklebust
2014-03-18 19:00         ` Steve Dickson
2014-03-18 19:50           ` Trond Myklebust
2014-03-19 12:39             ` Steve Dickson
2014-03-19 12:52               ` Trond Myklebust
2014-03-19 14:07                 ` Steve Dickson
2014-03-19 15:04                   ` Trond Myklebust
2014-03-19 17:10                     ` Steve Dickson
2014-03-19 17:29                       ` Trond Myklebust
2014-03-19 18:22                         ` Steve Dickson
2014-03-19 19:41                           ` Trond Myklebust
2014-03-20 14:12                             ` Steve Dickson
2014-03-20 15:19                               ` Steve Dickson
2014-03-18 18:47       ` Steve Dickson
2014-03-18 18:48 ` Steve Dickson
2014-04-14 16:25 ` Jeff Layton
2014-04-14 16:57   ` Trond Myklebust
2014-04-14 17:32     ` Jeff Layton

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=53289852.9050806@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.