public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	eduard.munteanu@linux360.ro, xiaoguangrong@cn.fujitsu.com,
	fweisbec@gmail.com, rostedt@goodmis.org, tglx@linutronix.de,
	mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:tracing/urgent] tracing: Fix trace_print_seq()
Date: Wed, 01 Jul 2009 17:15:59 +0300	[thread overview]
Message-ID: <1246457759.20817.2.camel@penberg-laptop> (raw)
In-Reply-To: <tip-5c37f525657e879a17a27c83021602cd55837531@git.kernel.org>

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@cn.fujitsu.com>
> AuthorDate: Wed, 1 Jul 2009 16:50:25 +0800
> Committer:  Ingo Molnar <mingo@elte.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@cn.fujitsu.com>
> Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Pekka Enberg <penberg@cs.helsinki.fi>
> LKML-Reference: <4A4B2351.5010300@cn.fujitsu.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>

Nice catch!

Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>


  reply	other threads:[~2009-07-01 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01  8:50 [PATCH] tracing: fix trace_print_seq() Xiao Guangrong
2009-07-01 14:01 ` Frederic Weisbecker
2009-07-02  5:57   ` Li Zefan
2009-07-01 14:06 ` [tip:tracing/urgent] tracing: Fix trace_print_seq() tip-bot for Xiao Guangrong
2009-07-01 14:15   ` Pekka Enberg [this message]
2009-07-01 14:42 ` tip-bot for Xiao Guangrong
2009-07-02  6:54 ` tip-bot for Xiao Guangrong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1246457759.20817.2.camel@penberg-laptop \
    --to=penberg@cs.helsinki.fi \
    --cc=eduard.munteanu@linux360.ro \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=xiaoguangrong@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox