* [Cluster-devel] [PATCH] GFS2: ignore unlock failures after withdraw
@ 2016-03-22 18:09 Benjamin Marzinski
2016-03-24 12:34 ` Bob Peterson
0 siblings, 1 reply; 2+ messages in thread
From: Benjamin Marzinski @ 2016-03-22 18:09 UTC (permalink / raw)
To: cluster-devel.redhat.com
After gfs2 has withdrawn the filesystem, it may still have many locks not
in the unlocked state. If it is using lock_dlm, it will failed trying
the unlocks since it has already unmounted the lock manager. Instead, it
should set the SDF_SKIP_DLM_UNLOCK flag on withdraw, to signal that
it can skip the lock_manager on unlocks, and failback to lock_nolock
style unlocking.
Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
---
fs/gfs2/glock.c | 9 ++++++++-
fs/gfs2/util.c | 1 +
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
index 6539131..2897ced 100644
--- a/fs/gfs2/glock.c
+++ b/fs/gfs2/glock.c
@@ -475,7 +475,14 @@ __acquires(&gl->gl_lockref.lock)
if (sdp->sd_lockstruct.ls_ops->lm_lock) {
/* lock_dlm */
ret = sdp->sd_lockstruct.ls_ops->lm_lock(gl, target, lck_flags);
- if (ret) {
+ if (ret == -EINVAL && gl->gl_target == LM_ST_UNLOCKED &&
+ target == LM_ST_UNLOCKED &&
+ test_bit(SDF_SKIP_DLM_UNLOCK, &sdp->sd_flags)) {
+ finish_xmote(gl, target);
+ if (queue_delayed_work(glock_workqueue, &gl->gl_work, 0) == 0)
+ gfs2_glock_put(gl);
+ }
+ else if (ret) {
pr_err("lm_lock ret %d\n", ret);
GLOCK_BUG_ON(gl, 1);
}
diff --git a/fs/gfs2/util.c b/fs/gfs2/util.c
index cf64583..aee4485 100644
--- a/fs/gfs2/util.c
+++ b/fs/gfs2/util.c
@@ -68,6 +68,7 @@ int gfs2_lm_withdraw(struct gfs2_sbd *sdp, const char *fmt, ...)
fs_err(sdp, "telling LM to unmount\n");
lm->lm_unmount(sdp);
}
+ set_bit(SDF_SKIP_DLM_UNLOCK, &sdp->sd_flags);
fs_err(sdp, "withdrawn\n");
dump_stack();
}
--
2.1.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* [Cluster-devel] [PATCH] GFS2: ignore unlock failures after withdraw
2016-03-22 18:09 [Cluster-devel] [PATCH] GFS2: ignore unlock failures after withdraw Benjamin Marzinski
@ 2016-03-24 12:34 ` Bob Peterson
0 siblings, 0 replies; 2+ messages in thread
From: Bob Peterson @ 2016-03-24 12:34 UTC (permalink / raw)
To: cluster-devel.redhat.com
----- Original Message -----
> After gfs2 has withdrawn the filesystem, it may still have many locks not
> in the unlocked state. If it is using lock_dlm, it will failed trying
> the unlocks since it has already unmounted the lock manager. Instead, it
> should set the SDF_SKIP_DLM_UNLOCK flag on withdraw, to signal that
> it can skip the lock_manager on unlocks, and failback to lock_nolock
> style unlocking.
>
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
Hi,
Thanks. This is now applied to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=3e11e530415027a57936545957126aff49267b76
Regards,
Bob Peterson
Red Hat File Systems
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-03-24 12:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-03-22 18:09 [Cluster-devel] [PATCH] GFS2: ignore unlock failures after withdraw Benjamin Marzinski
2016-03-24 12:34 ` Bob Peterson
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).