From: lhh@sourceware.org <lhh@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/fence/fenced recover.c
Date: 18 Sep 2007 20:53:48 -0000 [thread overview]
Message-ID: <20070918205348.16047.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: lhh at sourceware.org 2007-09-18 20:53:48
Modified files:
fence/fenced : recover.c
Log message:
Fix #258141 - possible use after free in fenced
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/fenced/recover.c.diff?cvsroot=cluster&r1=1.28&r2=1.29
--- cluster/fence/fenced/recover.c 2007/08/28 16:51:39 1.28
+++ cluster/fence/fenced/recover.c 2007/09/18 20:53:47 1.29
@@ -396,6 +396,7 @@
if (!error) {
list_del(&node->list);
free(node);
+ continue;
}
if (!comline.override_path) {
next reply other threads:[~2007-09-18 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 20:53 lhh [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-18 20:53 [Cluster-devel] cluster/fence/fenced recover.c lhh
2007-09-12 20:30 jparsons
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=20070918205348.16047.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).