From: Ben Greear <greearb@candelatech.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: Question on lockdep and MAX_LOCK_DEPTH
Date: Tue, 05 Feb 2013 22:23:50 -0800 [thread overview]
Message-ID: <5111F6F6.7010402@candelatech.com> (raw)
In-Reply-To: <1360125419.2621.39.camel@gandalf.local.home>
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:
>>
>> http://www.candelatech.com/~greearb/debug.tgz
>>
>
> 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....
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-02-06 6:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 1:10 Question on lockdep and MAX_LOCK_DEPTH Ben Greear
2013-02-06 1:54 ` Steven Rostedt
2013-02-06 2:17 ` Ben Greear
2013-02-06 2:26 ` Ben Greear
2013-02-06 2:52 ` Steven Rostedt
2013-02-06 3:30 ` Ben Greear
2013-02-06 4:36 ` Steven Rostedt
2013-02-06 6:23 ` Ben Greear [this message]
2013-02-06 13:21 ` Steven Rostedt
2013-02-06 15:56 ` Ben Greear
2013-02-06 16:07 ` Steven Rostedt
2013-02-06 16:39 ` Ingo Molnar
2013-02-06 16:46 ` Steven Rostedt
2013-02-06 16:58 ` Ben Greear
2013-02-06 17:03 ` Steven Rostedt
2013-02-06 4:26 ` Steven Rostedt
2013-02-06 6:20 ` 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=5111F6F6.7010402@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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