From: lhh@sourceware.org <lhh@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/rgmanager ChangeLog src/daemons/nodeev ...
Date: 21 Jun 2006 18:39:47 -0000 [thread overview]
Message-ID: <20060621183947.24603.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4U4
Changes by: lhh at sourceware.org 2006-06-21 18:39:46
Modified files:
rgmanager : ChangeLog
rgmanager/src/daemons: nodeevent.c
Log message:
Fix #194491
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/ChangeLog.diff?cvsroot=cluster&only_with_tag=RHEL4U4&r1=1.5.2.19&r2=1.5.2.19.2.1
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/src/daemons/nodeevent.c.diff?cvsroot=cluster&only_with_tag=RHEL4U4&r1=1.1.2.1&r2=1.1.2.1.2.1
--- cluster/rgmanager/ChangeLog 2006/06/16 20:11:33 1.5.2.19
+++ cluster/rgmanager/ChangeLog 2006/06/21 18:39:46 1.5.2.19.2.1
@@ -1,3 +1,7 @@
+2006-06-21 Lon Hohberger <lhh@redhat.com>
+ * src/daemons/nodeevent.c: Don't use the rg thread refcount in
+ node event handling (#194491)
+
2006-06-16 Lon Hohberger <lhh@redhat.com>
* src/daemons/fo_domain.c, groups.c: Get rid of compiler warnings
* src/daemons/rg_state.c: Change clu_lock_verbose to use the NULL
--- cluster/rgmanager/src/daemons/nodeevent.c 2006/05/12 21:28:31 1.1.2.1
+++ cluster/rgmanager/src/daemons/nodeevent.c 2006/06/21 18:39:46 1.1.2.1.2.1
@@ -60,7 +60,6 @@
/* Mutex held */
ne_thread = 0;
- rg_dec_threads();
pthread_mutex_unlock(&ne_queue_mutex);
return NULL;
}
@@ -96,8 +95,6 @@
pthread_create(&ne_thread, &attrs, node_event_thread, NULL);
pthread_attr_destroy(&attrs);
-
- rg_inc_threads();
}
pthread_mutex_unlock (&ne_queue_mutex);
}
next reply other threads:[~2006-06-21 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 18:39 lhh [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-21 18:34 [Cluster-devel] cluster/rgmanager ChangeLog src/daemons/nodeev lhh
2006-06-21 18:34 lhh
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=20060621183947.24603.qmail@sourceware.org \
--to=lhh@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).