From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.39-rc6-mmotm0506 - lockdep splat in RCU code on page fault
Date: Fri, 13 May 2011 00:18:50 -0700 [thread overview]
Message-ID: <20110513071850.GU2258@linux.vnet.ibm.com> (raw)
In-Reply-To: <5817.1305216324@localhost>
On Thu, May 12, 2011 at 12:05:24PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 12 May 2011 02:47:05 PDT, "Paul E. McKenney" said:
> > On Wed, May 11, 2011 at 07:11:34PM -0400, Valdis.Kletnieks@vt.edu wrote:
> > > My source has this:
> > >
> > > raw_spin_lock_irqsave(&rnp->lock, flags);
> > > rnp->wakemask |= rdp->grpmask;
> > > invoke_rcu_node_kthread(rnp);
> > > raw_spin_unlock_irqrestore(&rnp->lock, flags);
> > >
> > > the last 2 lines swapped from what you diffed against. I can easily work around
> > > that, except it's unclear what the implications of the invoke_rcu moving outside
> > > of the irq save/restore pair (or if it being inside is the actual root cause)...
> >
> > Odd...
> >
> > This looks to me like a recent -next -- I do not believe that straight
> > mmotm has rcu_cpu_kthread_timer() in it. The patch should apply to the
> > last few days' -next kernels.
>
> Ah. Found it. Your tree and current linux-next include this commit:
>
> commit 1217ed1ba5c67393293dfb0f03c353b118dadeb4
> tree a765356c8418e134de85fd05d9fe6eda41de859c tree | snapshot
> parent 29ce831000081dd757d3116bf774aafffc4b6b20 commit | diff
> rcu: permit rcu_read_unlock() to be called while holding runqueue locks
>
> which includes this chunk:
>
> @@ -1546,8 +1531,8 @@ static void rcu_cpu_kthread_timer(unsigned long arg)
>
> raw_spin_lock_irqsave(&rnp->lock, flags);
> rnp->wakemask |= rdp->grpmask;
> - invoke_rcu_node_kthread(rnp);
> raw_spin_unlock_irqrestore(&rnp->lock, flags);
> + invoke_rcu_node_kthread(rnp);
> }
>
>
> but that was committed 4 days ago, and Andrew pulled linux-next for the -mmotm
> 6 days ago, so it's not in there. The *rest* of your recent commits appear to
> be in there though. So that explains the patch failure to apply.
Whew!!! ;-)
Thanx, Paul
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-05-13 7:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 1:04 2.6.39-rc6-mmotm0506 - lockdep splat in RCU code on page fault Valdis.Kletnieks
2011-05-10 8:20 ` Paul E. McKenney
2011-05-10 8:57 ` Ingo Molnar
2011-05-10 16:21 ` Paul E. McKenney
2011-05-10 20:44 ` Ingo Molnar
2011-05-11 7:44 ` Paul E. McKenney
2011-05-11 23:11 ` Valdis.Kletnieks
2011-05-12 9:47 ` Paul E. McKenney
2011-05-12 16:05 ` Valdis.Kletnieks
2011-05-13 7:18 ` Paul E. McKenney [this message]
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=20110513071850.GU2258@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).