public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Chris Mason <chris.mason@oracle.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH 1/2] ftrace: fix trace_output
Date: Thu, 15 Jan 2009 17:40:08 -0800	[thread overview]
Message-ID: <20090115174008.935e0391.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090116004121.039250781@goodmis.org>

On Thu, 15 Jan 2009 19:40:51 -0500 Steven Rostedt <rostedt@goodmis.org> wrote:

> From: Lai Jiangshan <laijs@cn.fujitsu.com>
> 
> Impact: fix bug for handling partial line
> 
> trace_seq_printf(), seq_print_userip_objs(), ... return
> 0          -- partial line was written
> other(>0)  -- success
> 
> duplicate output is also removed in trace_print_raw().
> 
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> Signed-off-by: Steven Rostedt <srostedt@redhat.com>
> ---
>  kernel/trace/trace_output.c |   65 ++++++++++++++++++++----------------------
>  kernel/trace/trace_output.h |    4 +-
>  2 files changed, 33 insertions(+), 36 deletions(-)
> 
> diff --git a/kernel/trace/trace_output.c b/kernel/trace/trace_output.c
> index df0c25c..4e3ad36 100644
> --- a/kernel/trace/trace_output.c
> +++ b/kernel/trace/trace_output.c
> @@ -440,9 +440,9 @@ trace_fn_raw(struct trace_seq *s, struct trace_entry *entry, int flags)
>  
>  	trace_assign_type(field, entry);
>  
> -	if (trace_seq_printf(s, "%x %x\n",
> -			     field->ip,
> -			     field->parent_ip))
> +	if (!trace_seq_printf(s, "%x %x\n",

"%lx %lx", surely?

If trace_seq_printf() had the attribute(printf) thing, it would have warned.



  reply	other threads:[~2009-01-16  1:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16  0:40 [PATCH 0/2] ftrace: updates to tip Steven Rostedt
2009-01-16  0:40 ` [PATCH 1/2] ftrace: fix trace_output Steven Rostedt
2009-01-16  1:40   ` Andrew Morton [this message]
2009-01-16  1:46     ` Steven Rostedt
2009-01-16  0:40 ` [PATCH 2/2] ftrace: add stack trace to function tracer Steven Rostedt
2009-01-16  0:48   ` Steven Rostedt
2009-01-16 10:08   ` Frédéric Weisbecker
2009-01-16 14:28     ` Steven Rostedt
2009-01-16 11:19   ` Ingo Molnar
2009-01-16 11:23 ` [PATCH 0/2] ftrace: updates to tip Ingo Molnar
2009-01-16 13:08   ` Frédéric Weisbecker
2009-01-16 13:10     ` Ingo Molnar
2009-01-16 14:32   ` Steven Rostedt
2009-01-16 15:21     ` Ingo Molnar
2009-01-16 15:53       ` Steven Rostedt
2009-01-16 16:02         ` Ingo Molnar
2009-01-16 16:03           ` Ingo Molnar
2009-01-16 16:22           ` Steven Rostedt
2009-01-16 16:30             ` Ingo Molnar
2009-01-16 22:59               ` Ingo Molnar
2009-01-17  1:14                 ` Steven Rostedt
2009-01-17 13:48                   ` Frederic Weisbecker
2009-01-17 22:34                   ` Ingo Molnar
2009-01-18  7:27                     ` Ingo Molnar
2009-01-16 21:47 ` Chris Mason
2009-01-16 22:26   ` Ingo Molnar
2009-01-17  1:30     ` Chris Mason
2009-01-17  2:38     ` Arnaldo Carvalho de Melo
2009-01-19 13:31       ` Ingo Molnar

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=20090115174008.935e0391.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=fweisbec@gmail.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=srostedt@redhat.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