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:	Thu, 19 Feb 2009 09:17:28 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	"Luis Claudio R. Goncalves" <lclaudio@...g.org>
Subject: Re: [PATCH 0/6] [git pull] updates for tip/tracing/ftrace


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> > the function-graph-tracer started locking up since the last 
> > batch of changes:
> > 
> >  Testing tracer sysprof: .. no entries found ..FAILED!
> >  initcall 0xffffffff812e91d1 returned -1 after 101562 usecs
> >  initcall 0xffffffff812e91d1 returned with error code -1 
> >  calling  0xffffffff812e91e3 @ 1
> >  Testing tracer function: PASSED
> >  Testing dynamic ftrace: 
> >  [hard lockup]
> 
> I've successfully reproduced it with your config.
> Note that I didn't built the function graph tracer.
> 
> I also tried to set ftrace=nop as a parameter to avoid the selftests and then
> enabled the function tracer after the boot. And then I had no problem.
> 
> Looks like it happens during dynamic ftrace initialization.
> Perhaps a problem with the recent mutex conversion and kstopmachine, which
> could result in a hardlockup in case of a deadlock.
> 
> But lockdep didn't say anything.
> I'm reverting some of the last patches and will see.

Frederic, Steve, any progress on this bug? It's blocking all new 
tracing patches.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ