public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
	linux-kernel@vger.kernel.org, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
	josht@linux.vnet.ibm.com, dvhltc@us.ibm.com, niv@us.ibm.com,
	tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
	Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH -tip 0/2] Temporary RCU fixes for notrace and hotplug CPU
Date: Tue, 25 Aug 2009 09:12:08 -0700	[thread overview]
Message-ID: <20090825161208.GE6616@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090825080047.GA16139@elte.hu>

On Tue, Aug 25, 2009 at 10:00:47AM +0200, Ingo Molnar wrote:
> 
> btw., i'm still seeing crashes with the latest RCU bits:
> 
> [   20.621740] Testing event sys_enter_futex: OK
> [   20.629738] Testing event sys_exit_futex: OK
> [   20.637737] Testing event lock_acquire: [reboot]
> 
> Possibly due to infinite recursion as well. Config attached.

Color me confused...

Unless someone has a better idea, I will send in a patch that adds
"notrace" to every RCU API member used by any file in the kernel
that has "trace" in its name (excluding ptrace.c and rcutree_trace.c,
of course).  This list is as follows:

	call_rcu()
	call_rcu_sched()
	rcu_read_lock()
	rcu_read_unlock()

So, any better ideas?

							Thanx, Paul

  reply	other threads:[~2009-08-25 16:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 16:41 [PATCH -tip 0/2] Temporary RCU fixes for notrace and hotplug CPU Paul E. McKenney
2009-08-24 16:42 ` [PATCH -tip 1/2] Add "notrace" to RCU function headers used by ftrace Paul E. McKenney
2009-08-24 23:38   ` Steven Rostedt
2009-08-25  0:10     ` Mathieu Desnoyers
2009-08-25  2:02     ` Paul E. McKenney
2009-08-25  2:11       ` Steven Rostedt
2009-08-25  2:25         ` Paul E. McKenney
2009-08-25  7:13   ` [tip:core/rcu] rcu: " tip-bot for Paul E. McKenney
2009-08-24 16:42 ` [PATCH -tip 2/2] Add CPU-offline processing for single-node configurations Paul E. McKenney
2009-08-25  7:13   ` [tip:core/rcu] rcu: " tip-bot for Paul E. McKenney
2009-08-25  6:55 ` [PATCH -tip 0/2] Temporary RCU fixes for notrace and hotplug CPU Ingo Molnar
2009-08-25  8:00   ` Ingo Molnar
2009-08-25 16:12     ` Paul E. McKenney [this message]
2009-08-25 16:25       ` Mathieu Desnoyers
2009-08-25 17:11         ` Paul E. McKenney
2009-08-25 18:02           ` Mathieu Desnoyers
2009-08-25 18:36             ` [PATCH -tip] " Paul E. McKenney
2009-08-26  0:53               ` Lai Jiangshan
2009-08-26  1:31                 ` Paul E. McKenney
2009-08-25 15:40   ` Paul E. McKenney
2009-08-25 18:19     ` Ingo Molnar
2009-08-25 18:41       ` Paul E. McKenney
2009-08-25 18:21     ` [tip:core/rcu] rcu: Add #ifdef to suppress __rcu_offline_cpu() warning in !HOTPLUG_CPU builds tip-bot for 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=20090825161208.GE6616@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dipankar@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=josht@linux.vnet.ibm.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox