event_is_confchg needs to check for COROSYNC_EVENT_TYPE_NOTIFY instead of
COROSYNC_MSG_TYPE_NOTIFY as it operates on the higher level events.

Right now we never search for a notify event so it's not a problem in
practice.

Signed-off-by: Christoph Hellwig <[email protected]>

---
 sheep/cluster/corosync.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: sheepdog/sheep/cluster/corosync.c
===================================================================
--- sheepdog.orig/sheep/cluster/corosync.c      2012-07-06 11:51:34.243273289 
+0200
+++ sheepdog/sheep/cluster/corosync.c   2012-07-06 11:51:39.949939920 +0200
@@ -230,7 +230,7 @@ find_confchg_event(enum corosync_event_t
 static inline bool event_is_confchg(enum corosync_event_type type)
 {
        if (type == COROSYNC_EVENT_TYPE_BLOCK ||
-           type == COROSYNC_MSG_TYPE_NOTIFY)
+           type == COROSYNC_EVENT_TYPE_NOTIFY)
                return false;
 
        return true;
-- 
sheepdog mailing list
[email protected]
http://lists.wpkg.org/mailman/listinfo/sheepdog

Reply via email to