From: Guillaume Autran <gautran@mrv.com>
To: linux-net@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Possible BUG in IPv4 TCP window handling, all recent 2.4.x/2.6.x kernels
Date: Fri, 02 Sep 2005 12:18:52 -0400 [thread overview]
Message-ID: <43187B6C.7020203@mrv.com> (raw)
In-Reply-To: <20050902154424.GA15060@yakov.inr.ac.ru>
Hi Alexey,
Do you think this will also fix Ion's issue with small window size never
going back up ?
Thanks
Guillaume.
Alexey Kuznetsov wrote:
>Hello!
>
>
>
>>Here are the dumps...
>>
>>
>
>I see. It has nothing to do with clamping. Indeed this is a very old bug.
>Frankly speaking I even was aware about this at some moment
>(so that if the sender was Linux it would not happen. It was fixed there. :-))
>
>With such small window sender is forced to send a tiny segment
>via SWS override timer and receiver is confused in believing this
>is sender's mss, so the result is broken SWS avoidance.
>
>I think you can cure it deleting the following lines:
>
> /* If PSH is not set, packet should be
> * full sized, provided peer TCP is not badly broken.
> * This observation (if it is correct 8)) allows
> * to handle super-low mtu links fairly.
> */
> (len >= TCP_MIN_MSS + sizeof(struct tcphdr) &&
> !(tcp_flag_word(skb->h.th)&TCP_REMNANT))) {
>
>
>in tcp_input.c:tcp_measure_rcv_mss() at receiver side.
>
>
>Alexey
>
>
>
--
=======================================
Guillaume Autran
Senior Software Engineer
MRV Communications, Inc.
Tel: (978) 952-4932 office
E-mail: gautran@mrv.com
=======================================
next prev parent reply other threads:[~2005-09-02 16:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0509011713240.6083@guppy.limebrokerage.com>
[not found] ` <20050901.154300.118239765.davem@davemloft.net>
2005-09-01 22:53 ` Possible BUG in IPv4 TCP window handling, all recent 2.4.x/2.6.x kernels Ion Badulescu
2005-09-01 23:37 ` Jesper Juhl
2005-09-02 2:51 ` John Heffner
2005-09-02 6:28 ` David S. Miller
2005-09-02 14:05 ` lists
2005-09-02 14:10 ` John Heffner
2005-09-02 14:33 ` lists
2005-09-02 14:48 ` John Heffner
2005-09-02 15:43 ` Ion Badulescu
2005-09-02 13:02 ` Guillaume Autran
2005-09-02 13:48 ` Ion Badulescu
2005-09-02 13:52 ` Alexey Kuznetsov
2005-09-02 14:11 ` John Heffner
[not found] ` <43185E81.2070300@mrv.com>
[not found] ` <20050902154424.GA15060@yakov.inr.ac.ru>
2005-09-02 16:18 ` Guillaume Autran [this message]
[not found] ` <431877EE.6010101@mrv.com>
2005-09-02 17:32 ` Alexey Kuznetsov
2005-09-02 18:56 ` Guillaume Autran
2005-09-02 21:08 ` Alexey Kuznetsov
2005-09-02 13:48 ` Alexey Kuznetsov
2005-09-02 14:16 ` John Heffner
2005-09-02 15:11 ` Alexey Kuznetsov
2005-09-02 18:36 ` Alexey Kuznetsov
2005-09-02 20:57 ` Ion Badulescu
2005-09-02 21:18 ` Alexey Kuznetsov
2005-09-02 23:09 ` Ion Badulescu
2005-09-28 16:31 ` Ion Badulescu
2005-09-29 15:17 ` Alexey Kuznetsov
2005-09-29 15:34 ` Guillaume Autran
2005-09-29 16:04 ` John Heffner
2005-09-29 18:16 ` David S. Miller
2005-09-30 0:29 ` David S. Miller
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=43187B6C.7020203@mrv.com \
--to=gautran@mrv.com \
--cc=linux-net@vger.kernel.org \
--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).