From: David Miller <davem@davemloft.net>
To: komurojun@nifty.com
Cc: davem@sunset.davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC.
Date: Sat, 13 Oct 2007 15:52:11 -0700 (PDT) [thread overview]
Message-ID: <20071013.155211.92587020.davem@davemloft.net> (raw)
In-Reply-To: <20071014073658.d4352b8c.komurojun@nifty.com>
From: Komuro <komurojun@nifty.com>
Date: Sun, 14 Oct 2007 07:36:58 +0900
>
> Dear David
>
> The patch "[TCP]: Set initial_ssthresh default to zero in Cubic and BIC."
> is not very safe.
>
> With this patch, ftp-transfer stops in my system.
> (vsftpd-2.0.5-8)
>
> Please revert this patch.
No, I will not revert it with so little information, that would be a
knee-jerk reaction.
Let's anaylyze the problem first. Please:
1) Send this report to the correct place, which is netdev@vger.kernel.org,
so that the networking developers can analyze the bug. Most of
the core networking developers do not read linux-kernel so they
did not see your report.
2) Provide a test case that the developers can use the precisely
reproduce the problem. Your problem may be dependant upon the
remote system or infrastructure such as firewalls that sit between
your machine and the remote one, so it may instead be useful
to provide a tcpdump of the failing transfer.
I suspect some intermediate node, such as a firewall, is corrupting
your connection and causing the transfer to fail, and thus reverting
the BIC/CUBIC patch is just a workaround.
There are no other reports like your's and that change has been in
the tree for long enough to get substantial exposure.
next parent reply other threads:[~2007-10-13 22:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071006132601.f944f461.komurojun@nifty.com>
[not found] ` <20071014073658.d4352b8c.komurojun@nifty.com>
2007-10-13 22:52 ` David Miller [this message]
2007-10-13 22:54 ` [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC David Miller
[not found] ` <20071014100245.914b784a.komurojun@nifty.com>
2007-10-14 4:28 ` Komuro
2007-10-14 4:32 ` David Miller
2007-10-14 4:53 ` Komuro
2007-10-14 5:23 ` David Miller
2007-10-15 12:59 ` Komuro
2007-10-15 15:55 ` Stephen Hemminger
[not found] ` <20080302210716.69727582.komurojun-mbn@nifty.com>
2008-03-02 12:27 ` [BUG kernel 2.6.25-rc3 IPV6] ping6 -I eth0 ff02::1 causes system hang YOSHIFUJI Hideaki / 吉藤英明
2008-03-03 22:06 ` Komuro
2008-03-04 17:49 ` Brian Haley
2008-03-04 7:40 ` Andrew Morton
2008-03-08 4:44 ` Komuro
2008-03-08 5:20 ` Komuro
2008-03-08 11:56 ` David 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=20071013.155211.92587020.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davem@sunset.davemloft.net \
--cc=komurojun@nifty.com \
--cc=linux-kernel@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).