From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/group/daemon app.c
Date: 2 Aug 2006 20:30:36 -0000 [thread overview]
Message-ID: <20060802203036.11021.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: teigland at sourceware.org 2006-08-02 20:30:35
Modified files:
group/daemon : app.c
Log message:
before freeing a group struct, sanity check it's not referenced in
any recovery sets
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/daemon/app.c.diff?cvsroot=cluster&r1=1.38&r2=1.39
--- cluster/group/daemon/app.c 2006/07/19 19:45:53 1.38
+++ cluster/group/daemon/app.c 2006/08/02 20:30:35 1.39
@@ -656,6 +656,8 @@
void finalize_our_leave(group_t *g)
{
+ struct recovery_set *rs;
+ struct recovery_entry *re, *re2;
app_t *a = g->app;
log_group(g, "finalize_our_leave");
@@ -667,8 +669,19 @@
del_app_nodes(a);
free(a);
- /* FIXME: check if there are any recovery_sets
- referencing this group somehow */
+ /* this group shouldn't be in any recovery sets... sanity check
+ and avoid future segfault by removing re's referencing this g */
+
+ list_for_each_entry(rs, &recovery_sets, list) {
+ list_for_each_entry_safe(re, re2, &rs->entries, list) {
+ if (re->group == g) {
+ log_error(g, "finalize: still in recovery "
+ "set %d", rs->nodeid);
+ list_del(&rs->list);
+ free(rs);
+ }
+ }
+ }
remove_group(g);
}
next reply other threads:[~2006-08-02 20:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 20:30 teigland [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-16 15:52 [Cluster-devel] cluster/group/daemon app.c teigland
2006-10-12 14:25 teigland
2006-09-15 20:07 teigland
2006-09-14 20:56 teigland
2006-08-31 18:20 teigland
2006-08-22 14:36 teigland
2006-08-14 21:01 teigland
2006-07-19 19:45 teigland
2006-07-17 18:22 teigland
2006-07-17 17:06 rohara
2006-07-14 20:45 teigland
2006-07-16 7:51 ` Fabio Massimo Di Nitto
2006-07-17 17:08 ` Ryan O'Hara
2006-06-22 21:12 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=20060802203036.11021.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.