This patch causes the range calculated in messages_deliver_to_app() to
be negative in some circumstances (which triggers an assert).
The cases I've seen involve end_point being zero and
instance->my_high_delivered being positive.
The following patch appears to resolve the issue (ie. it allows range
to be negative instead of "really really positive") but may not be
100% correct.
--- a/exec/totemsrp.c Thu Oct 30 08:55:51 2008 +0100
+++ b/exec/totemsrp.c Fri Oct 31 10:25:13 2008 +0100
@@ -3427,7 +3460,7 @@ static void messages_deliver_to_app (
int res;
struct mcast *mcast_in;
struct mcast mcast_header;
- unsigned int range = 0;
+ int range = 0;
int endian_conversion_required;
unsigned int my_high_delivered_stored = 0;
On Wed, Oct 29, 2008 at 10:51, Steven Dake <[EMAIL PROTECTED]> wrote:
> In some circumstances the received_flg of the commit token is not
> properly configured. This patch addresses that issue by scanning the
> commit token on the first rotation for nodes in the previous ring id
> that are improperly set and setting them appropriately.
>
> Regards
> -steve
>
> _______________________________________________
> Openais mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/openais
>
_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais
