[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1246457759.20817.2.camel@penberg-laptop>
Date: Wed, 01 Jul 2009 17:15:59 +0300
From: Pekka Enberg <penberg@...helsinki.fi>
To: mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
eduard.munteanu@...ux360.ro, xiaoguangrong@...fujitsu.com,
fweisbec@...il.com, rostedt@...dmis.org, tglx@...utronix.de,
mingo@...e.hu
Cc: linux-tip-commits@...r.kernel.org
Subject: Re: [tip:tracing/urgent] tracing: Fix trace_print_seq()
On Wed, 2009-07-01 at 14:06 +0000, tip-bot for Xiao Guangrong wrote:
> Commit-ID: 5c37f525657e879a17a27c83021602cd55837531
> Gitweb: http://git.kernel.org/tip/5c37f525657e879a17a27c83021602cd55837531
> Author: Xiao Guangrong <xiaoguangrong@...fujitsu.com>
> AuthorDate: Wed, 1 Jul 2009 16:50:25 +0800
> Committer: Ingo Molnar <mingo@...e.hu>
> CommitDate: Wed, 1 Jul 2009 16:03:50 +0200
>
> 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@...fujitsu.com>
> Acked-by: Frederic Weisbecker <fweisbec@...il.com>
> Cc: Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
> Cc: Steven Rostedt <rostedt@...dmis.org>
> Cc: Pekka Enberg <penberg@...helsinki.fi>
> LKML-Reference: <4A4B2351.5010300@...fujitsu.com>
> Signed-off-by: Ingo Molnar <mingo@...e.hu>
Nice catch!
Acked-by: Pekka Enberg <penberg@...helsinki.fi>
--
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