[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090825161208.GE6616@linux.vnet.ibm.com>
Date: Tue, 25 Aug 2009 09:12:08 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Lai Jiangshan <laijs@...fujitsu.com>, linux-kernel@...r.kernel.org,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...ymtl.ca, josht@...ux.vnet.ibm.com,
dvhltc@...ibm.com, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org,
Paul Mundt <lethal@...ux-sh.org>
Subject: Re: [PATCH -tip 0/2] Temporary RCU fixes for notrace and hotplug CPU
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists