From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman-kernel/src cnxman.c membership.c
Date: 5 Feb 2008 16:21:15 -0000 [thread overview]
Message-ID: <20080205162115.16497.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL45
Changes by: pcaulfield at sourceware.org 2008-02-05 16:21:14
Modified files:
cman-kernel/src: cnxman.c membership.c
Log message:
Fix for cman throwing away messages that arrive out of order.
bz#430284
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman-kernel/src/cnxman.c.diff?cvsroot=cluster&only_with_tag=RHEL45&r1=1.42.2.28.2.1&r2=1.42.2.28.2.2
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman-kernel/src/membership.c.diff?cvsroot=cluster&only_with_tag=RHEL45&r1=1.44.2.26&r2=1.44.2.26.2.1
--- cluster/cman-kernel/src/Attic/cnxman.c 2007/04/02 08:03:13 1.42.2.28.2.1
+++ cluster/cman-kernel/src/Attic/cnxman.c 2008/02/05 16:21:14 1.42.2.28.2.2
@@ -867,8 +867,8 @@
/* Have we received this message before ? If so just ignore it, it's a
* resend for someone else's benefit */
if (!(flags & MSG_NOACK) &&
- rem_node && rem_node->last_seq_recv &&
- (short)((short)le16_to_cpu(header->seq) - (short)rem_node->last_seq_recv) <= 0) {
+ rem_node && rem_node->last_ackneeded_seq_recv &&
+ (short)((short)le16_to_cpu(header->seq) - (short)rem_node->last_ackneeded_seq_recv) <= 0) {
P_COMMS("Discarding message - seq = %d, last_seen = %d\n",
header->seq, rem_node->last_seq_recv);
/* Still need to ACK it though, in case it was the ACK that got
--- cluster/cman-kernel/src/Attic/membership.c 2007/01/19 16:20:14 1.44.2.26
+++ cluster/cman-kernel/src/Attic/membership.c 2008/02/05 16:21:14 1.44.2.26.2.1
@@ -1395,6 +1395,7 @@
cluster_members--;
node->state = NODESTATE_DEAD;
node->last_seq_recv = 0;
+ node->last_ackneeded_seq_recv = 0;
up(&cluster_members_lock);
send_nodedown(node->node_id, node->leave_reason);
@@ -1680,6 +1681,7 @@
newnode->us = 0;
newnode->leave_reason = 0;
newnode->last_seq_recv = 0;
+ newnode->last_ackneeded_seq_recv = 0;
newnode->last_seq_acked = 0;
newnode->last_seq_sent = 0;
newnode->incarnation++;
@@ -1714,6 +1716,7 @@
newnode->us = 0;
newnode->leave_reason = 0;
newnode->last_seq_recv = 0;
+ newnode->last_ackneeded_seq_recv = 0;
newnode->last_seq_acked = 0;
newnode->last_seq_sent = 0;
newnode->incarnation = 0;
next reply other threads:[~2008-02-05 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 16:21 pcaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-20 11:02 [Cluster-devel] cluster/cman-kernel/src cnxman.c membership.c pcaulfield
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=20080205162115.16497.qmail@sourceware.org \
--to=pcaulfield@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.