cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/dlm-kernel/src locking.c
Date: 14 Aug 2007 17:14:56 -0000	[thread overview]
Message-ID: <20070814171456.31759.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL4
Changes by:	teigland at sourceware.org	2007-08-14 17:14:55

Modified files:
	dlm-kernel/src : locking.c 

Log message:
	Just ignore user lock that's not in convert state during conversion
	deadlock check instead of asserting.  (This is code that's never
	touched by our own software, but someone's custom app hit it.)
	
	bz 240453: DLM locking assertion failure line 1390

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/dlm-kernel/src/locking.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.50.2.10&r2=1.50.2.11

--- cluster/dlm-kernel/src/Attic/locking.c	2007/01/03 16:10:27	1.50.2.10
+++ cluster/dlm-kernel/src/Attic/locking.c	2007/08/14 17:14:55	1.50.2.11
@@ -1432,7 +1432,8 @@
 	struct dlm_rsb *rsb = lkb->lkb_resource;
 	struct list_head *entry;
 
-	DLM_ASSERT(lkb->lkb_status == GDLM_LKSTS_CONVERT,);
+	if (lkb->lkb_status != GDLM_LKSTS_CONVERT)
+		return NULL;
 
 	/* Work our way up to the head of the queue looking for locks that
 	 * conflict with us */



             reply	other threads:[~2007-08-14 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 17:14 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-07 15:24 [Cluster-devel] cluster/dlm-kernel/src locking.c teigland
2006-06-22 14:29 teigland

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=20070814171456.31759.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 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).