public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFSD: NFSv4 callback client should use RPC_TASK_SOFTCONN
Date: Wed, 24 Feb 2010 20:51:45 -0500	[thread overview]
Message-ID: <20100225015145.GJ16665@fieldses.org> (raw)
In-Reply-To: <20100224214709.1399.59887.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

On Wed, Feb 24, 2010 at 01:48:06PM -0800, Chuck Lever wrote:
> The server's callback client should stop trying to connect to the
> client's callback server as soon as it gets ECONNREFUSED.
> 
> The NFS server's callback client does not call rpc_ping(), but appears
> to have it's own "ping" procedure, so it wasn't covered by commit
> caabea8a.
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> 
> Hi Bruce-
> 
> Noticed at Connectathon.  I think this is appropriate for 2.6.34, which opened
> today.

Thanks, applied for 2.6.34.

--b.

> 
>  fs/nfsd/nfs4callback.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4callback.c b/fs/nfsd/nfs4callback.c
> index c6eed2a..5ab598d 100644
> --- a/fs/nfsd/nfs4callback.c
> +++ b/fs/nfsd/nfs4callback.c
> @@ -542,7 +542,8 @@ void do_probe_callback(struct nfs4_client *clp)
>  	};
>  	int status;
>  
> -	status = rpc_call_async(cb->cb_client, &msg, RPC_TASK_SOFT,
> +	status = rpc_call_async(cb->cb_client, &msg,
> +				RPC_TASK_SOFT | RPC_TASK_SOFTCONN,
>  				&nfsd4_cb_probe_ops, (void *)clp);
>  	if (status) {
>  		warn_no_callback_path(clp, status);
> 

      parent reply	other threads:[~2010-02-25  1:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 21:48 [PATCH] NFSD: NFSv4 callback client should use RPC_TASK_SOFTCONN Chuck Lever
     [not found] ` <20100224214709.1399.59887.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-25  1:51   ` J. Bruce Fields [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=20100225015145.GJ16665@fieldses.org \
    --to=bfields@fieldses.org \
    --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