linux-kernel - Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no stop-machine, update stack tracer

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, 5 Jan 2012 10:19:16 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no
 stop-machine, update stack tracer


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

> On Wed, 2012-01-04 at 15:11 +0100, Ingo Molnar wrote:
> > * Steven Rostedt <rostedt@...dmis.org> wrote:
> > 
> > > My mistake, I forgot to add the "minimum config" for booting 
> > > the box. When I did that, it booted fine. I kicked off the 
> > > bisect again, and lets see what happens.
> > 
> > Okay.
> > 
> > I too did a lot of testing, breaking my promise to do other 
> > stuff ;-)
> > 
> > *Both* of your trees [the NMI and the cleanup/fixes tree], when 
> > merged produced hangs or spontaneous reboots, within 5 
> > iterations typically.
> 
> I actually haven't looked at the NMI branch yet. I'm still 
> trying to figure out why the ftrace one would lockup. I'll try 
> another box to see if that one also locks up on tip/master 
> with your config.

Any update on this?

I'm also seeing build failures with certain configs:

kernel/trace/trace_stack.c:387:3: error: implicit declaration of function ‘ftrace_set_early_filter’ 
[-Werror=implicit-function-declaration]

Thanks,

	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/