mirror of
https://git.proxmox.com/git/mirror_corosync
synced 2025-07-27 03:13:34 +00:00
Fix problem where corosync will segfault if there are gaps in recovery queue
Fixes a problem where there are gaps in the recovery queue. Example my_aru = 5, but there are messages at 7,8. 8 = my_high_seq_received which results in data slots taken up in new message queue. What should really happen is these last messages should be delivered after a transitional configuration to maintain SAFE agreement. We don't have support for SAFE atm, so it is probably safe just to throw these messages away. Without this change, the new message queue on a new configuraton change is out of sync. Signed-off-by: Steven Dake <sdake@redhat.com> Tested-by: Tim Beale <tlbeale@gmail.com> Reviewed-by: Jan Friesse <jfriesse@redhat.com>
This commit is contained in:
parent
57749ec02a
commit
a3d98f1652
@ -1809,7 +1809,7 @@ static void memb_state_operational_enter (struct totemsrp_instance *instance)
|
||||
sizeof (struct srp_addr) * instance->my_memb_entries);
|
||||
|
||||
instance->my_failed_list_entries = 0;
|
||||
instance->my_high_delivered = instance->my_aru;
|
||||
instance->my_high_delivered = instance->my_high_seq_received;
|
||||
|
||||
for (i = 0; i <= instance->my_high_delivered; i++) {
|
||||
void *ptr;
|
||||
|
Loading…
Reference in New Issue
Block a user