public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Liljeberg <Mika.Liljeberg@welho.com>
To: kuznet@ms2.inr.ac.ru, davem@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: TCP LAST-ACK state broken in 2.4.17-pre2
Date: Mon, 10 Dec 2001 20:16:07 +0200	[thread overview]
Message-ID: <3C14FBE7.E3A5F745@welho.com> (raw)

Hi,

I came across the following behavior (sorry, no tcpdump but this should
be easy to reproduce with the right tools):

hostA                 hostB
  --------FIN----------->
  <-----data+FIN---------
  --------ACK-------X       (packet lost)
  <-----data+FIN---------   (retransmit)
  <-----data+FIN---------   (retransmit)
  <-----data+FIN---------   (retransmit)
          ....
  <-----data+FIN---------   (retransmit)
  --------RST----------->

HostA is running Linux 2.4.17-pre2. HostB is running Symbian OS. All the
sequence numbers pan out.

Either LAST-ACK is completely broken or Linux just cannot handle a
FIN-ACK that is piggybacked on a data segment, when received in LAST-ACK
state. It should be acked as an out-of-window segment, as usual.
Finally, the LAST-ACK state times out and Linux responds to the FIN
segment with an RST.

Cheers,

	MikaL

             reply	other threads:[~2001-12-10 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10 18:16 Mika Liljeberg [this message]
2001-12-10 18:34 ` TCP LAST-ACK state broken in 2.4.17-pre2 kuznet
2001-12-10 18:54   ` Mika Liljeberg
2001-12-11 17:51     ` kuznet
2001-12-12 20:31       ` Mika Liljeberg
2001-12-13 17:59         ` kuznet
2001-12-13 19:30           ` Mika Liljeberg
2001-12-13 19:38             ` kuznet
2001-12-11  0:13   ` David S. Miller
2001-12-11 17:24     ` kuznet
  -- strict thread matches above, loose matches on Subject: below --
2001-12-13 10:19 Pasi Sarolahti

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=3C14FBE7.E3A5F745@welho.com \
    --to=mika.liljeberg@welho.com \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@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