From patchwork Wed Feb 19 13:44:38 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Junxiao Bi X-Patchwork-Id: 3681071 Return-Path: X-Original-To: patchwork-ocfs2-devel@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork1.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork1.web.kernel.org (Postfix) with ESMTP id BCA049F35F for ; Wed, 19 Feb 2014 13:46:03 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id BD09E201BA for ; Wed, 19 Feb 2014 13:46:02 +0000 (UTC) Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 33F3920155 for ; Wed, 19 Feb 2014 13:46:01 +0000 (UTC) Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s1JDj2Q9027698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Feb 2014 13:45:03 GMT Received: from oss.oracle.com (oss-external.oracle.com [137.254.96.51]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s1JDj1KN001930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Feb 2014 13:45:01 GMT Received: from localhost ([127.0.0.1] helo=oss.oracle.com) by oss.oracle.com with esmtp (Exim 4.63) (envelope-from ) id 1WG7SP-0007wF-4A; Wed, 19 Feb 2014 05:45:01 -0800 Received: from ucsinet22.oracle.com ([156.151.31.94]) by oss.oracle.com with esmtp (Exim 4.63) (envelope-from ) id 1WG7S3-0007vo-D2 for ocfs2-devel@oss.oracle.com; Wed, 19 Feb 2014 05:44:39 -0800 Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s1JDicix020283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 19 Feb 2014 13:44:39 GMT Received: from abhmp0008.oracle.com (abhmp0008.oracle.com [141.146.116.14]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s1JDick9017125; Wed, 19 Feb 2014 13:44:38 GMT MIME-Version: 1.0 Message-ID: Date: Wed, 19 Feb 2014 05:44:38 -0800 (PST) From: Junxiao Bi To: X-Mailer: Zimbra on Oracle Beehive Content-Disposition: inline Cc: mfasheh@suse.de, joe.jin@oracle.com, ocfs2-devel@oss.oracle.com Subject: Re: [Ocfs2-devel] [PATCH] ocfs2: dlm: fix recovery hung X-BeenThere: ocfs2-devel@oss.oracle.com X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ocfs2-devel-bounces@oss.oracle.com Errors-To: ocfs2-devel-bounces@oss.oracle.com X-Source-IP: acsinet21.oracle.com [141.146.126.237] X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_MED, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Hi Wengang, I thought about this changes before, it seemed may cause a deadlock. When the new recovery master is sending the RECO_BEGIN message, another node x may be trying to become the recovery master in dlm_pick_recovery_master(), at there, DLM_RECO_STATE_ACTIVE had been set before in dlm_do_recovery(), so the RECO_BEGIN message handler dlm_pick_recovery_master() can not be executed, then dlm->reco.new_master will not be set, so node x will loop in dlm_pick_recovery_master() forever. Thanks, Junxiao. ----- Original Message ----- From: wen.gang.wang@oracle.com To: junxiao.bi@oracle.com, ocfs2-devel@oss.oracle.com Cc: mfasheh@suse.de, joe.jin@oracle.com Sent: Wednesday, February 19, 2014 6:10:43 PM GMT +08:00 Beijing / Chongqing / Hong Kong / Urumqi Subject: Re: [Ocfs2-devel] [PATCH] ocfs2: dlm: fix recovery hung Seems DLM_RECO_STATE_FINALIZE is used to track the situation that the recovery master(node 0) dead (just) after it had finished the dlm recovery. So that the original dead node(node 1) needed not be recovered again. This flag is set only on non recovery master nodes. In this case, things looks like the recovery master reset "recover_master" and "dead node" after another node(node 2) had started to recover another dead node(node 3). This would happen only on the "old" recovery master(node 0). Note this flag DLM_RECO_STATE_ACTIVE, it's set only on master when it begins to recover and cleared when recovery finished. For an "old" master, checking DLM_RECO_STATE_ACTIVE makes sense. I'd like to suggest: thanks wengang ? 2014?02?19? 16:30, Junxiao Bi ??: > There is a race window in dlm_do_recovery() between dlm_remaster_locks() > and dlm_reset_recovery() when the recovery master nearly finish the recovery > process for a dead node. After the master sends FINALIZE_RECO message in > dlm_remaster_locks(), another node may become the recovery master for another > dead node, and then send the BEGIN_RECO message to all the nodes included the > old master, in the handler of this message dlm_begin_reco_handler() of old master, > dlm->reco.dead_node and dlm->reco.new_master will be set to the second dead > node and the new master, then in dlm_reset_recovery(), these two variables > will be reset to default value. This will cause new recovery master can not finish > the recovery process and hung, at last the whole cluster will hung for recovery. > > old recovery master: new recovery master: > dlm_remaster_locks() > become recovery master for > another dead node. > dlm_send_begin_reco_message() > dlm_begin_reco_handler() > { > if (dlm->reco.state & DLM_RECO_STATE_FINALIZE) { > return -EAGAIN; > } > dlm_set_reco_master(dlm, br->node_idx); > dlm_set_reco_dead_node(dlm, br->dead_node); > } > dlm_reset_recovery() > { > dlm_set_reco_dead_node(dlm, O2NM_INVALID_NODE_NUM); > dlm_set_reco_master(dlm, O2NM_INVALID_NODE_NUM); > } > will hung in dlm_remaster_locks() for > request dlm locks info > > Before send FINALIZE_RECO message, recovery master should set DLM_RECO_STATE_FINALIZE > for itself and clear it after the recovery done, this can break the race windows as > the BEGIN_RECO messages will not be handled before DLM_RECO_STATE_FINALIZE flag is > cleared. > > A similar race may happen between new recovery master and normal node which is in > dlm_finalize_reco_handler(), also fix it. > > Signed-off-by: Junxiao Bi > --- > fs/ocfs2/dlm/dlmrecovery.c | 11 +++++++++-- > 1 file changed, 9 insertions(+), 2 deletions(-) > > diff --git a/fs/ocfs2/dlm/dlmrecovery.c b/fs/ocfs2/dlm/dlmrecovery.c > index 7035af0..fe58e8b 100644 > --- a/fs/ocfs2/dlm/dlmrecovery.c > +++ b/fs/ocfs2/dlm/dlmrecovery.c > @@ -537,7 +537,10 @@ master_here: > /* success! see if any other nodes need recovery */ > mlog(0, "DONE mastering recovery of %s:%u here(this=%u)!\n", > dlm->name, dlm->reco.dead_node, dlm->node_num); > - dlm_reset_recovery(dlm); > + spin_lock(&dlm->spinlock); > + __dlm_reset_recovery(dlm); > + dlm->reco.state &= ~DLM_RECO_STATE_FINALIZE; > + spin_unlock(&dlm->spinlock); > } > dlm_end_recovery(dlm); > > @@ -695,6 +698,10 @@ static int dlm_remaster_locks(struct dlm_ctxt *dlm, u8 dead_node) > if (all_nodes_done) { > int ret; > > + spin_lock(&dlm->spinlock); > + dlm->reco.state |= DLM_RECO_STATE_FINALIZE; > + spin_unlock(&dlm->spinlock); > + > /* all nodes are now in DLM_RECO_NODE_DATA_DONE state > * just send a finalize message to everyone and > * clean up */ > @@ -2882,8 +2889,8 @@ int dlm_finalize_reco_handler(struct o2net_msg *msg, u32 len, void *data, > BUG(); > } > dlm->reco.state &= ~DLM_RECO_STATE_FINALIZE; > + __dlm_reset_recovery(dlm); > spin_unlock(&dlm->spinlock); > - dlm_reset_recovery(dlm); > dlm_kick_recovery_thread(dlm); > break; > default: Signed-off-by: Wengang Wang --- a/fs/ocfs2/dlm/dlmrecovery.c +++ b/fs/ocfs2/dlm/dlmrecovery.c @@ -2704,7 +2704,7 @@ int dlm_begin_reco_handler(struct o2net_msg *msg, u32 len, void *data, return 0; spin_lock(&dlm->spinlock); - if (dlm->reco.state & DLM_RECO_STATE_FINALIZE) { + if (dlm->reco.state & (DLM_RECO_STATE_FINALIZE | DLM_RECO_STATE_ACTIVE)) { mlog(0, "%s: node %u wants to recover node %u (%u:%u) " "but this node is in finalize state, waiting on finalize2\n", dlm->name, br->node_idx, br->dead_node,