tracing: add cpu_file intialization for ftrace_dump
commite543ad76914abec1acf6631604a4154cd7a2ca6b
authorSteven Rostedt <srostedt@redhat.com>
Wed, 4 Mar 2009 23:20:36 +0000 (4 18:20 -0500)
committerSteven Rostedt <srostedt@redhat.com>
Wed, 4 Mar 2009 23:32:28 +0000 (4 18:32 -0500)
treea2d093fe45ecb663fc1f977c0efc812ec06e1b99
parentefed792d6738964f399a508ef9e831cd60fa4657
tracing: add cpu_file intialization for ftrace_dump

Impact: fix to ftrace_dump output corruption

The commit: b04cc6b1f6398b0e0b60d37e27ce51b4899672ec
  tracing/core: introduce per cpu tracing files

added a new field to the iterator called cpu_file. This was a handle
to differentiate between the per cpu trace output files and the
all cpu "trace" file. The all cpu "trace" file required setting this
to TRACE_PIPE_ALL_CPU.

The problem is that the ftrace_dump sets up its own iterator but was
not updated to handle this change. The result was only CPU 0 printing
out on crash and a lot of "<0>"'s also being printed.

Reported-by: Thomas Gleixner <tglx@linuxtronix.de>
Tested-by: Darren Hart <dvhtc@us.ibm.com>
Signed-off-by: Steven Rostedt <srostedt@redhat.com>
kernel/trace/trace.c