* [Ocfs2-devel] [PATCH] ocfs2: cancel nn_still_up work when connection came up
@ 2012-09-04 2:31 Xue jiufei
0 siblings, 0 replies; only message in thread
From: Xue jiufei @ 2012-09-04 2:31 UTC (permalink / raw)
To: ocfs2-devel
We found that ocfs2 doesn't cancel the nn_still_up delayed work when
connection comes up. So if a node lost its connectivity and after a
while (more than idle time) the connection came up, it would still
make the quorum decision which we don't expect. And worse still, it
may result in an error of judgment if node detected another
connectivity lost just before the decision.
Signed-off-by: Xuejiufei <xuejiufei@huawei.com>
---
fs/ocfs2/cluster/tcp.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fs/ocfs2/cluster/tcp.c b/fs/ocfs2/cluster/tcp.c
index 1bfe880..8689f36 100644
--- a/fs/ocfs2/cluster/tcp.c
+++ b/fs/ocfs2/cluster/tcp.c
@@ -553,6 +553,7 @@ static void o2net_set_nn_state(struct o2net_node *nn,
if (!was_valid && valid) {
o2quo_conn_up(o2net_num_from_nn(nn));
+ cancel_deleyed_work(&nn->nn_still_up);
cancel_delayed_work(&nn->nn_connect_expired);
printk(KERN_NOTICE "o2net: %s " SC_NODEF_FMT "\n",
o2nm_this_node() > sc->sc_node->nd_num ?
--
1.7.8.6
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2012-09-04 2:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-04 2:31 [Ocfs2-devel] [PATCH] ocfs2: cancel nn_still_up work when connection came up Xue jiufei
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.