From: John Heffner <jheffner@psc.edu>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH] TCP FIN gets dropped prematurely, results in ack storm
Date: Tue, 01 May 2007 14:03:04 -0400 [thread overview]
Message-ID: <463780D8.2080105@psc.edu> (raw)
In-Reply-To: <20070501175340.GD1751@kvack.org>
Benjamin LaHaise wrote:
> On Tue, May 01, 2007 at 09:41:28PM +0400, Evgeniy Polyakov wrote:
>> Hmm, 2.2 machine in your test seems to behave incorrectly:
>
> I am aware of that. However, I think that the loss of certain packets and
> reordering can result in the same behaviour. What's more, is that this
> behaviour can occur in real deployed systems. "Be strict in what you send
> and liberal in what you accept." Both systems should be fixed, which is
> what I'm trying to do.
Actually, you cannot get in this situation by loss or reordering of
packets, only be corruption of state on one side. It sends the FIN,
which effectively increases the sequence number by one. However, all
later segments it sends have an old lower sequence number, which are now
out of window.
Being liberal in what you accept is good to a point, but sometimes you
have to draw the line.
-John
next prev parent reply other threads:[~2007-05-01 18:08 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 [this message]
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
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=463780D8.2080105@psc.edu \
--to=jheffner@psc.edu \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=johnpol@2ka.mipt.ru \
--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).