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]

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


* Steven Rostedt <rostedt@...dmis.org> wrote:

> > Now I've tested on x86-64 SMP and still nothing. Note that I've 
> > not only tested the selftests but also the function graph 
> > tracer. But nothing weird appeared.
> 
> I have not been able to trigger it either. I tested on three 
> different boxes, with various x86_64/32 configs as well.
> 
> One thing that seems to be common in these crashes is that they 
> all have rcu_torture running. Perhaps the function tracer is 
> widening a race window that is too small to trigger without the 
> tracing?

It's a highly elusive bug that seems to trigger only after hundreds 
of random kernel builds + reboots. Minor (and provably irrelevant) 
changes in .config details can make the bug go away, so it's not 
bisectabe.

But it only triggered on SMP kernels and on SMP systems so far, so 
the hotplug-race theory has a chance to be relevant.

> Paul suggested something about Lai's rcu_barrier fix?

I'm looking at that now. The function-tracer self-test will trigger 
stop_machine_run(), which brings CPUs down, correct? That would 
indeed make sense. Will know in 1-2 days whether the hangs go away.

	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/