From: Daniel Borkmann <daniel@iogearbox•net>
To: David Miller <davem@davemloft•net>, ncardwell@google•com
Cc: stephen@networkplumber•org, netdev@vger•kernel.org,
matiasb@gmail•com, ycheng@google•com, edumazet@google•com
Subject: Re: [Bug 94991] New: TCP bug creates additional RTO in very specific condition
Date: Tue, 17 Mar 2015 18:53:11 +0100 [thread overview]
Message-ID: <55086A07.9080309@iogearbox.net> (raw)
In-Reply-To: <20150317.134443.687799973483992041.davem@davemloft.net>
On 03/17/2015 06:44 PM, David Miller wrote:
> From: Neal Cardwell <ncardwell@google•com>
> Date: Tue, 17 Mar 2015 12:49:49 -0400
>
>> On Tue, Mar 17, 2015 at 11:33 AM, Stephen Hemminger
>> <stephen@networkplumber•org> wrote:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=94991
>>> Bug ID: 94991
>>> Summary: TCP bug creates additional RTO in very specific
>>> condition
>>
>> Thanks for forwarding. I posted the following on the bug:
>>
>> 2.6.32 is over 5 years old (Dec 2009). I suspect this bug is in the
>> old FRTO code that Yuchung removed when he rewrote FRTO from scratch
>> in 2013. Can you please test a newer version of the kernel (preferably
>> 3.19 but at least 3.12 or newer) to see if this bug is still around?
>> Thanks!
>
> Stephen, if you're processing networking bugzilla entries in the
> future, don't even forward 2.6.x based stuff to the list please.
That's btw a RHEL6 kernel it seems (2.6.32-504.3.3.el6.x86_64).
Matias, you would need to open a BZ at https://bugzilla.redhat.com/
for RHEL6 kernel component.
prev parent reply other threads:[~2015-03-17 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 15:33 Fw: [Bug 94991] New: TCP bug creates additional RTO in very specific condition Stephen Hemminger
2015-03-17 16:49 ` Neal Cardwell
2015-03-17 17:44 ` David Miller
2015-03-17 17:53 ` Daniel Borkmann [this message]
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=55086A07.9080309@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=matiasb@gmail$(echo .)com \
--cc=ncardwell@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
--cc=ycheng@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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