From: Jeff Layton <jlayton@kernel.org>
To: Dai Ngo <dai.ngo@oracle.com>, trondmy@hammerspace.com, anna@kernel.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SUNRPC: remove the maximum number of retries in call_bind_status
Date: Wed, 19 Apr 2023 06:06:56 -0400 [thread overview]
Message-ID: <63ccdf13db934fdbca46233b6dd961f54d47c6e8.camel@kernel.org> (raw)
In-Reply-To: <1681849142-28597-1-git-send-email-dai.ngo@oracle.com>
On Tue, 2023-04-18 at 13:19 -0700, Dai Ngo wrote:
> Currently call_bind_status places a hard limit of 3 to the number of
> retries on EACCES error. This limit was done to prevent NLM unlock
> requests from being hang forever when the server keeps returning garbage.
> However this change causes problem for cases when NLM service takes
> longer than 9 seconds to register with the port mapper after a restart.
>
> This patch removes this hard coded limit and let the RPC handles
> the retry based on the standard hard/soft task semantics.
>
> Fixes: 0b760113a3a1 ("NLM: Don't hang forever on NLM unlock requests")
> Reported-by: Helen Chao <helen.chao@oracle.com>
> Tested-by: Helen Chao <helen.chao@oracle.com>
> Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
> ---
> include/linux/sunrpc/sched.h | 3 +--
> net/sunrpc/clnt.c | 3 ---
> net/sunrpc/sched.c | 1 -
> 3 files changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/include/linux/sunrpc/sched.h b/include/linux/sunrpc/sched.h
> index b8ca3ecaf8d7..8ada7dc802d3 100644
> --- a/include/linux/sunrpc/sched.h
> +++ b/include/linux/sunrpc/sched.h
> @@ -90,8 +90,7 @@ struct rpc_task {
> #endif
> unsigned char tk_priority : 2,/* Task priority */
> tk_garb_retry : 2,
> - tk_cred_retry : 2,
> - tk_rebind_retry : 2;
> + tk_cred_retry : 2;
> };
>
> typedef void (*rpc_action)(struct rpc_task *);
> diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
> index 0b0b9f1eed46..63b438d8564b 100644
> --- a/net/sunrpc/clnt.c
> +++ b/net/sunrpc/clnt.c
> @@ -2050,9 +2050,6 @@ call_bind_status(struct rpc_task *task)
> status = -EOPNOTSUPP;
> break;
> }
> - if (task->tk_rebind_retry == 0)
> - break;
> - task->tk_rebind_retry--;
> rpc_delay(task, 3*HZ);
> goto retry_timeout;
> case -ENOBUFS:
> diff --git a/net/sunrpc/sched.c b/net/sunrpc/sched.c
> index be587a308e05..c8321de341ee 100644
> --- a/net/sunrpc/sched.c
> +++ b/net/sunrpc/sched.c
> @@ -817,7 +817,6 @@ rpc_init_task_statistics(struct rpc_task *task)
> /* Initialize retry counters */
> task->tk_garb_retry = 2;
> task->tk_cred_retry = 2;
> - task->tk_rebind_retry = 2;
>
> /* starting timestamp */
> task->tk_start = ktime_get();
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-04-19 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 20:19 [PATCH] SUNRPC: remove the maximum number of retries in call_bind_status Dai Ngo
2023-04-19 10:06 ` Jeff Layton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-08 18:45 Dai Ngo
2023-03-08 18:50 ` Chuck Lever III
2023-03-08 19:03 ` dai.ngo
2023-03-14 16:19 ` dai.ngo
2023-04-06 17:33 ` Jeff Layton
2023-04-06 18:10 ` Jeff Layton
2023-04-06 19:36 ` dai.ngo
2023-04-06 19:43 ` Chuck Lever III
2023-04-06 19:59 ` Jeff Layton
2023-04-06 20:58 ` dai.ngo
2023-04-06 21:51 ` Jeff Layton
2023-04-06 20:58 ` dai.ngo
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=63ccdf13db934fdbca46233b6dd961f54d47c6e8.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=anna@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.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