From: kuznet@ms2.inr.ac.ru
To: manfred@colorfullife.COM (Manfred Spraul)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.16 through 2.2.18preX TCP hang bug triggered by rsync
Date: Wed, 24 Jan 2001 23:03:34 +0300 (MSK) [thread overview]
Message-ID: <200101242003.XAA21040@ms2.inr.ac.ru> (raw)
In-Reply-To: <3A6E02E6.B3261E1@colorfullife.com> from "Manfred Spraul" at Jan 24, 1 11:15:01 am
Hello!
> I read through the tcpdump, and it seems that Linux completely ignores
> packets with out-of-window sequence numbers:
Yes, Linux is __very__ not right doing this. RFC requires to accept
ACK, URG and RST on any segment adjacent to window, even if window
is zero.
Solaris also does thing, formally wrong, but it would work if linux
would be formally correct.
O-ho-ho... It is difficult bug.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-24 20:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 22:17 Linux 2.2.16 through 2.2.18preX TCP hang bug triggered by rsync Manfred Spraul
2001-01-23 22:59 ` Manfred Spraul
2001-01-24 20:03 ` kuznet [this message]
2001-01-24 20:34 ` Manfred Spraul
2001-01-24 20:42 ` kuznet
2001-01-25 18:35 ` kuznet
2001-01-24 20:56 ` Andi Kleen
2001-01-25 10:58 ` Matthias Andree
2001-01-25 12:17 ` James Sutherland
2001-01-25 12:27 ` Matthias Andree
2001-01-25 11:32 ` David S. Miller
2001-01-25 11:40 ` Andi Kleen
2001-01-25 11:44 ` David S. Miller
2001-01-25 11:56 ` Andi Kleen
2001-01-25 12:25 ` James Sutherland
-- strict thread matches above, loose matches on Subject: below --
2001-01-26 20:56 Dave Dykstra
2001-01-27 18:27 ` kuznet
2001-01-25 12:24 Studierende der Universitaet des Saarlandes
2001-01-25 12:34 ` Andi Kleen
2001-01-23 20:42 Dave Dykstra
2001-01-23 22:51 ` Dave Dykstra
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=200101242003.XAA21040@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.COM \
/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