From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] TCP FIN gets dropped prematurely, results in ack storm
Date: Tue, 1 May 2007 22:20:07 +0400 [thread overview]
Message-ID: <20070501182006.GA12030@2ka.mipt.ru> (raw)
In-Reply-To: <20070501151354.GB1751@kvack.org>
On Tue, May 01, 2007 at 11:13:54AM -0400, Benjamin LaHaise (bcrl@kvack.org) wrote:
> Hello,
>
> While testing a failover scenario, I managed to trigger an ack storm
> between a Linux box and another system. Although the cause of this particular
> ACK storm was due to the other box forgetting that it sent out a FIN (the
> second node was unaware of the FIN the first sent in its dying gasp, which
> is what I'm trying to fix, but it's a tricky race), the resulting Linux
> behaviour wasn't very robust. Is there any particularly good reason that
One of the packets sent by broken 1.1 host has incorrect checksum, so it
will be dropped by 2.2 system in theory, could that packet somehow break
2.2 stack's state machine?
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-05-01 18:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 15:13 [PATCH] TCP FIN gets dropped prematurely, results in ack storm Benjamin LaHaise
2007-05-01 16:20 ` Evgeniy Polyakov
2007-05-01 16:49 ` Benjamin LaHaise
2007-05-01 17:41 ` Evgeniy Polyakov
2007-05-01 17:53 ` Benjamin LaHaise
2007-05-01 18:03 ` John Heffner
2007-05-01 19:19 ` Benjamin LaHaise
2007-05-01 20:24 ` David Miller
2007-05-01 17:57 ` Evgeniy Polyakov
2007-05-01 18:02 ` Evgeniy Polyakov
2007-05-01 17:54 ` John Heffner
2007-05-01 18:04 ` Benjamin LaHaise
2007-05-01 18:07 ` Evgeniy Polyakov
2007-05-01 18:20 ` Evgeniy Polyakov [this message]
2007-05-01 18:25 ` Evgeniy Polyakov
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=20070501182006.GA12030@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).