From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v2 0/3] gfs2: Misc withdraw patches
Date: Tue, 2 Aug 2022 12:58:08 -0500 [thread overview]
Message-ID: <20220802175811.438067-1-rpeterso@redhat.com> (raw)
This is version 2 which simplifies patch 1 and clarifies the comments of
patch 2 as per Andreas Gruenbacher's suggestions.
This patch set fixes a few bugs in how gfs2 handles file systems after
withdraw. In an ideal world, after a file system is withdrawn, users
should be able to unmount the file system without problems. However, we
discovered three problems that prevented clean unmounts:
1. A duplicate iput of the journal after attempted recovery caused
kernel panics after withdraw.
2. After withdraw, unmount would hang for its alloted timeout period
when glocks had waiters queued that, due to the withdraw, could
never be granted.
3. Unmount would similarly hang when the withdraw prevented an outgoing
request to dlm, but so the glock was never unlocked.
Bob Peterson (3):
gfs2: Prevent double iput for journal on error
gfs2: Dequeue waiters when withdrawn
gfs2: Clear GLF_LOCK when withdraw prevents xmote
fs/gfs2/glock.c | 33 ++++++++++++++++++++++++++++++++-
fs/gfs2/glock.h | 1 +
fs/gfs2/util.c | 6 ++++++
3 files changed, 39 insertions(+), 1 deletion(-)
--
2.36.1
next reply other threads:[~2022-08-02 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 17:58 Bob Peterson [this message]
2022-08-02 17:58 ` [Cluster-devel] [PATCH 1/3] gfs2: Prevent double iput for journal on error Bob Peterson
2022-08-02 17:58 ` [Cluster-devel] [PATCH 2/3] gfs2: Dequeue waiters when withdrawn Bob Peterson
2022-08-02 17:58 ` [Cluster-devel] [PATCH 3/3] gfs2: Clear GLF_LOCK when withdraw prevents xmote Bob Peterson
2022-08-05 13:13 ` Andreas Gruenbacher
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=20220802175811.438067-1-rpeterso@redhat.com \
--to=rpeterso@redhat.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;
as well as URLs for NNTP newsgroup(s).