From: Cen Zhang <zzzccc427@gmail.com>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>,
Heming Zhao <heming.zhao@suse.com>
Subject: Re: [PATCH] ocfs2/cluster: reject local node clears while heartbeat runs
Date: Tue, 16 Jun 2026 15:45:10 +0800 [thread overview]
Message-ID: <CAFRLqsU_PdYYdKejY83CeKWoYx++6eNeFFa9SwR4o2irNJtjCA@mail.gmail.com> (raw)
In-Reply-To: <84ecad6e-4072-46e5-a2ab-3dbfe5c48476@linux.alibaba.com>
Hi Joseph,
> Seems a simple fix for this issue is also clearing cluster->cl_has_local
> in the same path?
Thanks for your review.
Yes, clearing cluster->cl_has_local in that path is needed. I updated the
patch to do that.
While checking this path again, I found that clearing cl_has_local alone
does not cover the running heartbeat thread case. After local=0,
o2nm_this_node() still returns O2NM_MAX_NODES, which has the same value as
O2NM_INVALID_NODE_NUM, and the heartbeat thread can still use that value
for hr_slots[] or for the final node undepend path.
So in v2 I kept the local node number stable in the heartbeat region once
the region starts, used that stored node for heartbeat I/O and teardown,
and also cleared cl_has_local in o2nm_node_local_store() as you suggested.
I will send v2 shortly.
Best regards,
Cen Zhang
next prev parent reply other threads:[~2026-06-16 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 5:33 Cen Zhang
2026-06-16 6:33 ` Joseph Qi
2026-06-16 7:45 ` Cen Zhang [this message]
2026-06-21 11:17 ` XIAO WU
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=CAFRLqsU_PdYYdKejY83CeKWoYx++6eNeFFa9SwR4o2irNJtjCA@mail.gmail.com \
--to=zzzccc427@gmail.com \
--cc=baijiaju1990@gmail.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
/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
all inboxes | Powered by JetHome®