From: Benjamin LaHaise <bcrl@kvack.org>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
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 12:49:35 -0400 [thread overview]
Message-ID: <20070501164935.GC1751@kvack.org> (raw)
In-Reply-To: <20070501162050.GB21896@2ka.mipt.ru>
On Tue, May 01, 2007 at 08:20:50PM +0400, Evgeniy Polyakov wrote:
> > http://www.kvack.org/~bcrl/ack-storm.log . As near as I can tell, a
> > similar effect can occur between two Linux boxes if the right packets get
> > reordered/dropped during connection teardown.
>
> Could you archive 24Mb file or cut more precise bits out of it?
The interesting bits are the first 10 lines.
> According to your patch, several packets with fin bit might be sent,
> including one with data. If another host does not receive fin
> retransmit, then that logic is broken, and it can not be fixed by
> duplicating fins, I would even say, that remote box should drop second
> packet with fin, while it can carry data, which will break higher
> connection logic.
The FIN hasn't been ack'd by the other side, though and yet Linux is no
longer transmitting packets with it sent. Read the beginning of the trace.
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <zyntrop@kvack.org>.
next prev parent reply other threads:[~2007-05-01 16:49 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 [this message]
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
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=20070501164935.GC1751@kvack.org \
--to=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).