From: Sasha Levin <levinsasha928@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: rcu,sched: spinlock recursion on 3.5-rc2
Date: Tue, 12 Jun 2012 17:31:01 +0200 [thread overview]
Message-ID: <1339515061.4999.102.camel@lappy> (raw)
In-Reply-To: <1339514114.31548.78.camel@twins>
On Tue, 2012-06-12 at 17:15 +0200, Peter Zijlstra wrote:
> On Tue, 2012-06-12 at 17:07 +0200, Thomas Gleixner wrote:
> > Hmm, not sure. The deadlock was not triggered in switch_to. It was
> > just at the beginning of __schedule()
> >
> >
> How can you tell? switch_to() is a macro not a function, it won't ever
> show up on a stack-trace.. but I think you meant context_switch() but
> that typically gets inlined, similar problem.
addr2line -i confirmed it was pointing to switch_to(), if it matters.
btw, wouldn't it be nice if there were a short script that would take an
oops and convert all those kernel addresses into file+line numbers based
on a given vmlinux? It would make our lives so much easier.
next prev parent reply other threads:[~2012-06-12 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 11:35 rcu,sched: spinlock recursion on 3.5-rc2 Sasha Levin
2012-06-12 13:40 ` Thomas Gleixner
2012-06-12 14:47 ` Paul E. McKenney
2012-06-12 15:07 ` Thomas Gleixner
2012-06-12 15:15 ` Peter Zijlstra
2012-06-12 15:20 ` Thomas Gleixner
2012-06-12 15:25 ` Paul E. McKenney
2012-06-12 15:31 ` Sasha Levin [this message]
2012-06-12 15:22 ` Paul E. McKenney
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=1339515061.4999.102.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.