From: Li Zefan <lizf@cn.fujitsu.com>
To: Liming Wang <liming.wang@windriver.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: don't increment @pos in g_start()
Date: Fri, 19 Jun 2009 17:45:36 +0800 [thread overview]
Message-ID: <4A3B5E40.8040607@cn.fujitsu.com> (raw)
In-Reply-To: <1245401968-25235-1-git-send-email-liming.wang@windriver.com>
Liming Wang wrote:
> how about this one?
>
Yeah, this should work, and cleaner than my version.
> It's wrong to increment @pos in g_start(). It causes some entries
> lost when reading set_graph_function, if the output of the file
> is large than PAGE_SIZE.
>
> [ Impact: fix missing entries when reading set_graph_function ]
>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> Signed-off-by: Liming Wang <liming.wang@windriver.com>
> ---
> kernel/trace/ftrace.c | 14 +++++---------
> 1 files changed, 5 insertions(+), 9 deletions(-)
>
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index 134e580..1beaac6 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -2495,29 +2495,25 @@ static void *
> g_next(struct seq_file *m, void *v, loff_t *pos)
> {
> unsigned long *array = m->private;
> - int index = *pos;
>
> - (*pos)++;
> + if (v)
> + (*pos)++;
>
> - if (index >= ftrace_graph_count)
> + if (*pos >= ftrace_graph_count)
> return NULL;
>
> - return &array[index];
> + return &array[*pos];
> }
>
> static void *g_start(struct seq_file *m, loff_t *pos)
> {
> - void *p = NULL;
> -
> mutex_lock(&graph_lock);
>
> /* Nothing, tell g_show to print all functions are enabled */
> if (!ftrace_graph_count && !*pos)
> return (void *)1;
>
> - p = g_next(m, p, pos);
> -
> - return p;
> + return g_next(m, NULL, pos);
> }
>
> static void g_stop(struct seq_file *m, void *p)
next prev parent reply other threads:[~2009-06-19 9:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 6:42 [PATCH 0/5] tracing: seqfile fixes Li Zefan
2009-06-19 6:45 ` [PATCH 1/5] tracing/events: don't increment @pos in s_start() Li Zefan
2009-06-19 6:46 ` [PATCH 2/5] tracing_bprintk: don't increment @pos in t_start() Li Zefan
2009-06-19 9:39 ` Wang Liming
2009-06-22 0:38 ` Li Zefan
2009-06-22 2:08 ` Wang Liming
2009-06-22 3:01 ` Li Zefan
2009-06-19 6:46 ` [PATCH 3/5] trace_stat: don't increment @pos in stat_seq_start() Li Zefan
2009-06-19 6:47 ` [PATCH 4/5] ftrace: don't increment @pos in g_start() Li Zefan
2009-06-19 8:59 ` [PATCH] " Liming Wang
2009-06-19 9:45 ` Li Zefan [this message]
2009-06-22 0:45 ` Li Zefan
2009-06-22 2:42 ` Wang Liming
2009-06-22 3:15 ` Li Zefan
2009-06-22 3:08 ` Wang Liming
2009-06-19 6:48 ` [PATCH 5/5] tracing: reset iterator in t_start() Li Zefan
2009-06-23 6:48 ` Wang Liming
2009-06-23 7:19 ` Li Zefan
2009-06-23 7:19 ` Wang Liming
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=4A3B5E40.8040607@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=liming.wang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.