From: Srinivas Eeda <srinivas.eeda@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v2] ocfs2: o2net: fix connect expired
Date: Thu, 30 Oct 2014 23:29:42 -0700 [thread overview]
Message-ID: <54532C56.5010204@oracle.com> (raw)
In-Reply-To: <1414735683-26646-1-git-send-email-junxiao.bi@oracle.com>
looks good. Thanks for your explanation and fix
Reviewed-by: Srinivas Eeda <srinivas.eeda@oracle.com>
On 10/30/2014 11:08 PM, Junxiao Bi wrote:
> Set nn_persistent_error to -ENOTCONN will stop reconnect since the
> "stop" condition in o2net_start_connect() will be true.
>
> stop = (nn->nn_sc ||
> (nn->nn_persistent_error &&
> (nn->nn_persistent_error != -ENOTCONN || timeout == 0)));
>
> This will make connection never be established if the first connection request
> is lost.
>
> Set nn_persistent_error to 0 when connect expired to fix this. With this
> changes, dlm will not be waken up when connect expired, this is OK since
> dlm depends on network, dlm can do nothing in this case if waken up. Let
> it wait there for network recover and connect built again to continue.
>
> Signed-off-by: Junxiao Bi <junxiao.bi@oracle.com>
> ---
> fs/ocfs2/cluster/tcp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/cluster/tcp.c b/fs/ocfs2/cluster/tcp.c
> index 97de0fb..4d6b645 100644
> --- a/fs/ocfs2/cluster/tcp.c
> +++ b/fs/ocfs2/cluster/tcp.c
> @@ -1736,7 +1736,7 @@ static void o2net_connect_expired(struct work_struct *work)
> o2net_idle_timeout() / 1000,
> o2net_idle_timeout() % 1000);
>
> - o2net_set_nn_state(nn, NULL, 0, -ENOTCONN);
> + o2net_set_nn_state(nn, NULL, 0, 0);
> }
> spin_unlock(&nn->nn_lock);
> }
prev parent reply other threads:[~2014-10-31 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 6:08 [Ocfs2-devel] [PATCH v2] ocfs2: o2net: fix connect expired Junxiao Bi
2014-10-31 6:29 ` Srinivas Eeda [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=54532C56.5010204@oracle.com \
--to=srinivas.eeda@oracle.com \
--cc=ocfs2-devel@oss.oracle.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