From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: ignore unlock failures after withdraw
Date: Thu, 24 Mar 2016 08:34:08 -0400 (EDT) [thread overview]
Message-ID: <425387913.42613341.1458822848882.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1458670187-26408-1-git-send-email-bmarzins@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
prev parent reply other threads:[~2016-03-24 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 18:09 [Cluster-devel] [PATCH] GFS2: ignore unlock failures after withdraw Benjamin Marzinski
2016-03-24 12:34 ` Bob Peterson [this message]
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=425387913.42613341.1458822848882.JavaMail.zimbra@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.