From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, RHEL4, updated. gfs-kernel_2_6_9_76-52-g82270e2
Date: 5 May 2008 18:43:56 -0000 [thread overview]
Message-ID: <20080505184356.10309.qmail@sourceware.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=82270e2e03d662a31e7372fa1abfcbd65feb30a7
The branch, RHEL4 has been updated
via 82270e2e03d662a31e7372fa1abfcbd65feb30a7 (commit)
from 60e3a142329558117f4ed4ebeb48deb496ecf0d6 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 82270e2e03d662a31e7372fa1abfcbd65feb30a7
Author: David Teigland <teigland@redhat.com>
Date: Mon May 5 13:43:16 2008 -0500
lock_dlm: ignore dlm EBUSY on plock unlock
bz 432707
The previous commit for this bug didn't resolve all the cases of
EBUSY assertions from plock unlocks. As suggested in the previous
commit message, this patch just ignores -EBUSY errors returned for
plock unlocks instead of asserting.
Signed-off-by: David Teigland <teigland@redhat.com>
-----------------------------------------------------------------------
Summary of changes:
gfs-kernel/src/dlm/lock.c | 12 ++++++++++--
1 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/gfs-kernel/src/dlm/lock.c b/gfs-kernel/src/dlm/lock.c
index bd71c2c..2528314 100644
--- a/gfs-kernel/src/dlm/lock.c
+++ b/gfs-kernel/src/dlm/lock.c
@@ -354,8 +354,16 @@ void do_dlm_unlock(dlm_lock_t *lp)
error = dlm_unlock(lp->dlm->gdlm_lsp, lp->lksb.sb_lkid, lkf, NULL, lp);
-
- DLM_ASSERT(!error || (plock && error == -EINPROGRESS),
+ if (plock) {
+ if (error == -EINPROGRESS || error == -EBUSY) {
+ log_all("do_dlm_unlock %x,%"PRIx64" flags %lx error %d",
+ lp->lockname.ln_type, lp->lockname.ln_number,
+ lp->flags, error);
+ return;
+ }
+ }
+
+ DLM_ASSERT(!error,
printk("%s: error=%d num=%x,%"PRIx64" lkf=%x flags=%lx\n",
lp->dlm->fsname, error, lp->lockname.ln_type,
lp->lockname.ln_number, lp->lkf, lp->flags););
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-05-05 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080505184356.10309.qmail@sourceware.org \
--to=teigland@sourceware.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 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.