Apparent issue with fragmentation and config changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Actually, I tried something that seems to work for me. I have no idea what the possible side effects are, but, if nothing else, it illustrates my point. Patch attached.

J-C
> 
diff -ru corosync-1.4.6.orig/exec/totemsrp.c corosync-1.4.6.fixed/exec/totemsrp.c
--- corosync-1.4.6.orig/exec/totemsrp.c	2013-05-29 07:33:27.000000000 -0700
+++ corosync-1.4.6.fixed/exec/totemsrp.c	2013-12-07 22:03:33.824349319 -0800
@@ -1790,12 +1790,13 @@
 		left_list, instance->my_left_memb_entries,
 		0, 0, &instance->my_ring_id);
 	instance->waiting_trans_ack = 1;
-	instance->totemsrp_waiting_trans_ack_cb_fn (1);
 
 // TODO we need to filter to ensure we only deliver those
 // messages which are part of instance->my_deliver_memb
 	messages_deliver_to_app (instance, 1, instance->old_ring_state_high_seq_received);
 
+	instance->totemsrp_waiting_trans_ack_cb_fn (1);
+
 	instance->my_aru = aru_save;
 
 	/*
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss

[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux