From: Eric Dumazet <eric.dumazet@gmail.com>
To: Rob Herring <robherring2@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: panics in tcp_ack
Date: Mon, 03 Jun 2013 08:58:17 -0700 [thread overview]
Message-ID: <1370275097.24311.158.camel@edumazet-glaptop> (raw)
In-Reply-To: <51ACBB86.6010702@gmail.com>
On Mon, 2013-06-03 at 10:51 -0500, Rob Herring wrote:
> Any ideas on what could cause that? Anything the driver could be doing
> or not doing to cause it? Perhaps some memory ordering or visibility issue.
>
Yes, maybe, but I have no idea.
> > Your best bet would be to perform a (reverse) bisection if you know
> > recent kernels are OK.
>
> I did that once looking at 3.6 and 3.7 stable kernels, but they did not
> have fixes like "tcp: fix skb_availroom()" and so I just hit other
> failures. I'll do it again with more fixes applied.
Yes, you'll have to apply a number of known fixes at every step of the
bisection, sorry !
next prev parent reply other threads:[~2013-06-03 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 0:16 panics in tcp_ack Rob Herring
2013-06-03 0:24 ` Eric Dumazet
2013-06-03 0:26 ` Eric Dumazet
2013-06-03 0:36 ` Eric Dumazet
2013-06-03 2:23 ` Rob Herring
2013-06-03 3:03 ` Eric Dumazet
2013-06-03 3:18 ` Rob Herring
2013-06-03 3:32 ` Eric Dumazet
2013-06-03 3:41 ` Rob Herring
2013-06-03 13:05 ` Rob Herring
2013-06-03 13:25 ` Eric Dumazet
2013-06-03 15:51 ` Rob Herring
2013-06-03 15:58 ` Eric Dumazet [this message]
2013-06-14 19:12 ` Rob Herring
2013-06-14 20:52 ` Eric Dumazet
2013-06-06 17:21 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2013-06-03 0:13 Rob Herring
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=1370275097.24311.158.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=robherring2@gmail.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