From: Junxiao Bi via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, stable@vger.kernel.org,
piaojun@huawei.com, mark@fasheh.com, joseph.qi@linux.alibaba.com,
jlbec@evilplan.org, heming.zhao@suse.com, ghe@suse.com,
gechangwei@live.cn, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [merged mm-hotfixes-stable] revert-ocfs2-mount-shared-volume-without-ha-stack.patch removed from -mm tree
Date: Mon, 18 Jul 2022 11:07:11 -0700 [thread overview]
Message-ID: <70bfaa1f-9a33-406f-3998-e185daea48b3@oracle.com> (raw)
In-Reply-To: <20220717043751.51CD1C341C0@smtp.kernel.org>
Hi Andrew,
Can you help fix below "From:" to "From: Junxiao Bi <junxiao.bi@oracle.com>"
Thanks,
Junxiao.
On 7/16/22 9:37 PM, Andrew Morton wrote:
> From: Junxiao Bi via Ocfs2-devel<ocfs2-devel@oss.oracle.com>
> Subject: Revert "ocfs2: mount shared volume without ha stack"
> Date: Fri, 3 Jun 2022 15:28:01 -0700
>
> This reverts commit 912f655d78c5d4ad05eac287f23a435924df7144.
>
> This commit introduced a regression that can cause mount hung. The
> changes in __ocfs2_find_empty_slot causes that any node with none-zero
> node number can grab the slot that was already taken by node 0, so node 1
> will access the same journal with node 0, when it try to grab journal
> cluster lock, it will hung because it was already acquired by node 0.
> It's very easy to reproduce this, in one cluster, mount node 0 first, then
> node 1, you will see the following call trace from node 1.
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2022-07-18 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 4:37 [Ocfs2-devel] [merged mm-hotfixes-stable] revert-ocfs2-mount-shared-volume-without-ha-stack.patch removed from -mm tree Andrew Morton via Ocfs2-devel
2022-07-18 18:07 ` Junxiao Bi via Ocfs2-devel [this message]
2022-07-18 22:10 ` Andrew Morton via Ocfs2-devel
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=70bfaa1f-9a33-406f-3998-e185daea48b3@oracle.com \
--to=ocfs2-devel@oss.oracle.com \
--cc=akpm@linux-foundation.org \
--cc=gechangwei@live.cn \
--cc=ghe@suse.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=junxiao.bi@oracle.com \
--cc=mark@fasheh.com \
--cc=mm-commits@vger.kernel.org \
--cc=piaojun@huawei.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).