From: Ben Greear <greearb@candelatech.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: 3.9.5+: Crash in tcp_input.c:4810.
Date: Mon, 08 Jul 2013 10:23:51 -0700 [thread overview]
Message-ID: <51DAF5A7.60505@candelatech.com> (raw)
In-Reply-To: <1372827749.4979.52.camel@edumazet-glaptop>
On 07/02/2013 10:02 PM, Eric Dumazet wrote:
> On Tue, 2013-07-02 at 21:49 -0700, Ben Greear wrote:
>
>> Well, network emulators are easy to come by in the office.... Maybe running
>> a bunch of TCP connections through a lossy network would exercise this code
>> path a bit? Aside from random pkt loss, any other types of network conditions
>> that might help trigger this faster?
>>
>> I'll set up some tests using some wired ethernet...if we can trigger it there
>> then we at least know it doesn't depend on ath9k...
>
> I tried a lot of things, including netem with many reorders and/or
> packetdrill tests, but so far not a single warning from tcp_collapse()
We ran a 5+ day test using un-modified 3.10 kernel and did not trigger
the bug.
So, I'm guessing the problem is either fixed upstream or is exacerbated
or caused by our local patches. Sometime soon we'll start porting local
patches to newer kernels...we'll see what happens then.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-07-08 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 18:08 3.9.5+: Crash in tcp_input.c:4810 Ben Greear
2013-06-17 18:17 ` Eric Dumazet
2013-06-21 19:26 ` Ben Greear
2013-07-01 18:10 ` Ben Greear
2013-07-03 1:04 ` Eric Dumazet
2013-07-03 3:21 ` Ben Greear
2013-07-03 4:41 ` Eric Dumazet
2013-07-03 4:49 ` Ben Greear
2013-07-03 5:02 ` Eric Dumazet
2013-07-08 17:23 ` Ben Greear [this message]
2013-07-08 18:21 ` Eric Dumazet
2013-07-08 18:30 ` Ben Greear
2013-07-08 19:01 ` Eric Dumazet
2013-07-08 19:59 ` Ben Greear
2013-07-08 20:10 ` Eric Dumazet
2013-07-08 20:17 ` Ben Greear
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=51DAF5A7.60505@candelatech.com \
--to=greearb@candelatech.com \
--cc=eric.dumazet@gmail.com \
--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).