[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1370275097.24311.158.camel@edumazet-glaptop>
Date: Mon, 03 Jun 2013 08:58:17 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Rob Herring <robherring2@...il.com>
Cc: netdev@...r.kernel.org
Subject: Re: panics in tcp_ack
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 !
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists