From: lhh@sourceware.org <lhh@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/rgmanager ChangeLog src/daemons/restree.c
Date: 13 Jun 2007 20:12:20 -0000 [thread overview]
Message-ID: <20070613201220.24633.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: lhh at sourceware.org 2007-06-13 20:12:19
Modified files:
rgmanager : ChangeLog
rgmanager/src/daemons: restree.c
Log message:
Fix #229650 - part 2; fixes an uninitialized var problem
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/ChangeLog.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.31.2.10&r2=1.31.2.11
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/src/daemons/restree.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.23.2.4&r2=1.23.2.5
--- cluster/rgmanager/ChangeLog 2007/05/31 18:58:46 1.31.2.10
+++ cluster/rgmanager/ChangeLog 2007/06/13 20:12:19 1.31.2.11
@@ -1,3 +1,6 @@
+2007-06-13 Lon Hohberger <lhh@redhat.com>
+ * src/daemons/restree.c: Fix #229650 uninitialized bug
+
2007-05-31 Lon Hohberger <lhh@redhat.com>
* src/daemons/resrules.c: Fix #234249 - ignore obvious backup files
in /usr/share/cluster when processing resource rules
--- cluster/rgmanager/src/daemons/restree.c 2007/05/31 18:58:46 1.23.2.4
+++ cluster/rgmanager/src/daemons/restree.c 2007/06/13 20:12:19 1.23.2.5
@@ -509,6 +509,7 @@
node->rn_parent = parent;
node->rn_resource = curres;
node->rn_state = RES_STOPPED;
+ node->rn_flags = 0;
node->rn_actions = (resource_act_t *)act_dup(curres->r_actions);
snprintf(tok, sizeof(tok), "%s/@__independent_subtree", base);
next reply other threads:[~2007-06-13 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 20:12 lhh [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-25 21:09 [Cluster-devel] cluster/rgmanager ChangeLog src/daemons/restree.c lhh
2007-09-25 21:06 lhh
2007-06-18 20:51 lhh
2007-06-13 20:13 lhh
2006-06-16 20:11 lhh
2006-06-16 20:11 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=20070613201220.24633.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).