From: Sasha Levin <levinsasha928@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: Peter Zijlstra <peterz@infradead.org>,
Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: rcu: BUG: spinlock recursion on CPU#3, trinity-child19/5970
Date: Mon, 02 Jul 2012 16:36:53 +0200 [thread overview]
Message-ID: <1341239813.2958.7.camel@lappy> (raw)
In-Reply-To: <20120702142252.GA22868@linux.vnet.ibm.com>
On Mon, 2012-07-02 at 07:22 -0700, Paul E. McKenney wrote:
> > OK, so it looks like the context-switch-time call into preemptible RCU
> > needs to be outside of the runqueue-lock critical section. One way
> > to do this is be reverting 616c310e (Move PREEMPT_RCU preemption to
> > switch_to() invocation). Sasha, could you please try this out?
>
> Hmmmm... Here is a patch for this reversion on top of -rcu with
> conflicts resolved.
It looks like how I've resolved it.
Just for clarity, the only rcu related patch I have on top of -next is
this reversal one. I've dropped anything we tested before.
Looks like its running fine for a bit now (~10 min). I'll ping if
anything changes, but on the other tests it has usually failed at this
point.
next prev parent reply other threads:[~2012-07-02 14:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 10:09 rcu: BUG: spinlock recursion on CPU#3, trinity-child19/5970 Sasha Levin
2012-06-29 17:23 ` Paul E. McKenney
2012-06-29 21:40 ` Sasha Levin
2012-06-29 22:27 ` Paul E. McKenney
2012-06-29 22:40 ` Sasha Levin
2012-06-29 23:01 ` Paul E. McKenney
2012-07-02 10:32 ` Peter Zijlstra
2012-07-02 11:35 ` Paul E. McKenney
2012-07-02 11:59 ` Peter Zijlstra
2012-07-02 13:12 ` Sasha Levin
2012-07-02 13:33 ` Paul E. McKenney
2012-07-02 14:22 ` Paul E. McKenney
2012-07-02 14:36 ` Sasha Levin [this message]
2012-07-02 14:59 ` Paul E. McKenney
2012-07-04 14:54 ` Sasha Levin
2012-07-04 19:07 ` Paul E. McKenney
2012-06-30 11:36 ` Sasha Levin
2012-06-30 13:14 ` Paul E. McKenney
2012-06-30 13:28 ` Sasha Levin
2012-06-30 13:58 ` 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=1341239813.2958.7.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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