public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: cfeist@sourceware.org To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com Subject: Cluster Project branch, RHEL47, updated. gfs-kernel_2_6_9_76-52-g4565fc4 Date: Mon, 05 May 2008 19:27:00 -0000 [thread overview] Message-ID: <20080505192709.10570.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=4565fc4f11ec6af1498cd60d787fd584b6a949a0 The branch, RHEL47 has been updated via 4565fc4f11ec6af1498cd60d787fd584b6a949a0 (commit) from 71f39467f02f161b1af03fe36a2fe4aac2488ee2 (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 4565fc4f11ec6af1498cd60d787fd584b6a949a0 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> bz 440665 (for 4.6.z) ----------------------------------------------------------------------- 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 19:27 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=20080505192709.10570.qmail@sourceware.org \ --to=cfeist@sourceware.org \ --cc=cluster-cvs@sources.redhat.com \ --cc=cluster-devel@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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).