linux-kernel - Re: [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Mar 2009 19:36:42 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace


* Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:

> On Thu, Mar 19, 2009 at 01:21:47PM -0400, Steven Rostedt wrote:
> > 
> > I'm still not able to reproduce, but...
> > 
> > On Thu, 19 Mar 2009, Ingo Molnar wrote:
> > 
> > > * Ingo Molnar <mingo@...e.hu> wrote:
> > > 
> > > > these latest ftrace changes caused a lockup on a -tip testsystem:
> > > 
> > > Note, even with Rusty's offstack-cpumask fix applied (in latest 
> > > -tip), i can reproduce a lockup:
> > > 
> 
> [ . . . ]
> 
> > This looks like it is RCU/stop_machine related. The CPU is stuck in
> > in stop_machine? I see that rcu_torture is running. Does this go away if 
> > you turn off rcu_torture?
> 
> Grasping at straws...  Does Lai's rcu_barrier() fix help?

which one is that?

	Ingo
--
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/