tracing: Fix trace_print_seq()
authorXiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Wed, 1 Jul 2009 08:50:25 +0000 (16:50 +0800)
committerIngo Molnar <mingo@elte.hu>
Thu, 2 Jul 2009 06:51:13 +0000 (08:51 +0200)
commite1af3aec3e2e7d21d4b3054323779d478c19d907
tree338ef5a081fb66a6463ab4c1e882d7870ca154ac
parent4a2bb6fcc80e6330ca2f2393e98605052cc7780b
tracing: Fix trace_print_seq()

We will lose something if trace_seq->buffer[0] is 0, because the copy length
is calculated by strlen() in seq_puts(), so using seq_write() instead of
seq_puts().

There have a example:
after reboot:

 # echo kmemtrace > current_tracer
 # echo 0 > options/kmem_minimalistic
 # cat trace
 # tracer: kmemtrace
 #
 #

Nothing is exported, because the first byte of trace_seq->buffer[ ]
is KMEMTRACE_USER_ALLOC.

( the value of KMEMTRACE_USER_ALLOC is zero, seeing
  kmemtrace_print_alloc_user() in kernel/trace/kmemtrace.c)

Signed-off-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
Acked-by: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: Steven Rostedt <rostedt@goodmis.org>
LKML-Reference: <4A4B2351.5010300@cn.fujitsu.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
kernel/trace/trace_output.c