From: Li Zefan <lizf@cn.fujitsu.com>
To: Wang Liming <liming.wang@windriver.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] tracing: reset iterator in t_start()
Date: Tue, 23 Jun 2009 15:19:44 +0800 [thread overview]
Message-ID: <4A408210.5000208@cn.fujitsu.com> (raw)
In-Reply-To: <4A407AB0.3000703@windriver.com>
> Another version:
> Since we have saved current (struct tracer *) in m->private in .next, in
> .start, we don't need to call .next to find the one that should be
> printed in 2nd or nth time.
>
I don't like this for 2 reasons.
1. It's strange that @pos is not incremented in next().
2.
t_stop()
mutex_unlock()
unregister_tracer(t)
t_start()
mutex_lock()
t = m->private
...
t = t-next.
We access t->next though @t was unregistered. This is not
good, though it does no harm here.
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index cae34c6..02cdccc 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -2055,8 +2055,6 @@ t_next(struct seq_file *m, void *v, loff_t *pos)
> {
> struct tracer *t = m->private;
>
> - (*pos)++;
> -
> if (t)
> t = t->next;
>
> @@ -2068,11 +2066,8 @@ t_next(struct seq_file *m, void *v, loff_t *pos)
> static void *t_start(struct seq_file *m, loff_t *pos)
> {
> struct tracer *t = m->private;
> - loff_t l = 0;
>
> mutex_lock(&trace_types_lock);
> - for (; t && l < *pos; t = t_next(m, t, &l))
> - ;
>
> return t;
> }
>
>
next prev parent reply other threads:[~2009-06-23 7:18 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
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 [this message]
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=4A408210.5000208@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=fweisbec@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox