public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: lhh@sourceware.org
To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com
Subject: Cluster Project branch, RHEL4, updated. gfs-kernel_2_6_9_76-66-g532a3cd
Date: Tue, 27 May 2008 21:55:00 -0000	[thread overview]
Message-ID: <20080527215506.20841.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=532a3cdbc09cfc0dfd85296ccc613f2753acce22

The branch, RHEL4 has been updated
       via  532a3cdbc09cfc0dfd85296ccc613f2753acce22 (commit)
      from  b9a120827b951c81b2e9a2b631698fa92311c04f (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 532a3cdbc09cfc0dfd85296ccc613f2753acce22
Author: Lon Hohberger <lhh@redhat.com>
Date:   Tue May 27 17:54:53 2008 -0400

    [rgmanager] Fix if() clause which broke VF locking with gulm plugin
    
    Resolves bz448108

-----------------------------------------------------------------------

Summary of changes:
 rgmanager/src/clulib/vft.c |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/rgmanager/src/clulib/vft.c b/rgmanager/src/clulib/vft.c
index 29e51bc..fea3a2c 100644
--- a/rgmanager/src/clulib/vft.c
+++ b/rgmanager/src/clulib/vft.c
@@ -1257,7 +1257,7 @@ vf_write(cluster_member_list_t *membership, uint32_t flags, char *keyid,
 	uint32_t totallen;
 	struct timeval start, end, dif;
 	void *lockp = NULL;
-	int l;
+	int l = 1; /* keep track of whether we got a lock */
 	char lock_name[256];
 	int my_status;
 	int ret_status = 0;
@@ -1434,7 +1434,11 @@ out_cleanup:
 	 */
 	if (join_view)
 		free(join_view);
-	if (lockp)
+	if (l == 0) /* from clu_lock() above - if 0,
+		       we have a lock to release.  Note that vf_read
+		       uses 'l' for another use; maybe we should
+		       clean it up for maintenance.  This fixes
+		       bugzilla #448108 */
 		clu_unlock(lock_name, lockp);
 
 	pthread_mutex_unlock(&vf_mutex);


hooks/post-receive
--
Cluster Project


                 reply	other threads:[~2008-05-27 21:55 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=20080527215506.20841.qmail@sourceware.org \
    --to=lhh@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).