From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman-kernel/src cnxman.c
Date: 1 Nov 2007 10:44:26 -0000 [thread overview]
Message-ID: <20071101104426.25137.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: pcaulfield at sourceware.org 2007-11-01 10:44:25
Modified files:
cman-kernel/src: cnxman.c
Log message:
When checking for old messages, compare against the last ACKed message rather
than the last seen message (which could be a NOACK message). otherwise we end
up throwing awa messages if they arrive out of order.
bz#299061
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman-kernel/src/cnxman.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.42.2.29&r2=1.42.2.30
--- cluster/cman-kernel/src/Attic/cnxman.c 2007/03/30 07:50:49 1.42.2.29
+++ cluster/cman-kernel/src/Attic/cnxman.c 2007/11/01 10:44:25 1.42.2.30
@@ -868,7 +868,7 @@
* 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) {
+ (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
@@ -3284,7 +3284,7 @@
{
struct cl_barrier *barrier = (struct cl_barrier *) arg;
- /* Ignore any futher messages, they are too late. */
+ /* Ignore any further messages, they are too late. */
barrier->phase = 0;
/* and cause it to timeout */
next reply other threads:[~2007-11-01 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 10:44 pcaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-14 16:10 [Cluster-devel] cluster/cman-kernel/src cnxman.c pcaulfield
2007-04-02 8:03 pcaulfield
2007-03-30 7:50 pcaulfield
2007-02-27 10:38 pcaulfield
2007-02-27 10:37 pcaulfield
2007-01-19 10:24 pcaulfield
2007-01-19 10:23 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=20071101104426.25137.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).