Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, nostop-machine, update stack tracer

[Ingo Molnar]

* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

> On Sat, 2012-01-07 at 13:25 +0100, Ingo Molnar wrote:
> > * Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> > 
> > > > 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]
> > > 
> > > Hmm, your right. It depends on dyn_ftrace to be configured. 
> > > Strange that my tests didn't catch that as I thought one of my 
> > > tests compiles with static ftrace. I'll have to look into why 
> > > my test didn't catch that. I'll send a fix later today.
> > 
> > Hm, i cannot re-test this tree with general randconfig until it 
> > keeps failing the build. I'll test the NMI bits, to be able to 
> > exclude those.
> 
> 
> Ingo,
> 
> I updated the branch by adding the below patch that fixes the bug. You
> can apply this and then run your tests again.
> 
> Thanks!
> 
> Please pull the latest tip/perf/core tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> tip/perf/core
> 
> Head SHA1: 96de37b62ca525cd77d2e85aea1472846ee31c4d
> 
> 
> Steven Rostedt (1):
>       tracing: Fix compile error when static ftrace is enabled
> 
> ----
>  include/linux/ftrace.h |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)

Pulled, thanks Steve!

I don't get those spontaneous reboots in regular randconfig 
tests so far - so lets wait until a simpler config triggers it - 
chances are high that the problem was unrelated to your tree, it 
just happened to trigger it somehow.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/