[lkml]   [2013]   [Feb]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Question on lockdep and MAX_LOCK_DEPTH
On 02/06/2013 05:21 AM, Steven Rostedt wrote:
> On Tue, 2013-02-05 at 22:23 -0800, Ben Greear wrote:
>> On 02/05/2013 08:36 PM, Steven Rostedt wrote:
>>> On Tue, 2013-02-05 at 19:30 -0800, Ben Greear wrote:
>>>> It's huge, so here's a link:
>>> The trace shows that __netif_receive_skb() is grabbing an
>>> rcu_read_lock() but never releasing it. But I don't see any possible way
>>> that can be true in the code.
>>> Can you apply the following patch and run the trace again. I'd like to
>>> see if the code is going in the path I expect it is.
>> I'll look at this in detail tomorrow. I have a few patches in dev.c code, maybe
>> I merged something badly....
> I wish you told me that in the beginning. That you modified the core
> code. In that case I would have asked to see your modifications before
> anything else.
> I'm 99% sure that the bug is in your modifications.

I'm sorry, I tried to make that clear.

My tree is here, minus a few debugging patches related to this bug:;a=summary

It's rebased on top of 3.7.6.

The wanlink module I'm using is outside the tree. I recently decided to
release this as GPL, so ignore any conflicting copyright notices to
the contrary in the code:

The wanlink module is a network impairment tool that acts like a 2-port
bridge. In my current test case, I'm bridging about 300Mbps of traffic
across two ethernet ports. It blows up immediately after starting the


Ben Greear <>
Candela Technologies Inc

 \ /
  Last update: 2013-02-06 17:42    [W:0.047 / U:6.660 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site