From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing - fix function graph trace to properly display failed entries
Date: Mon, 7 Dec 2009 21:21:49 +0100 [thread overview]
Message-ID: <20091207202146.GE5049@nowhere> (raw)
In-Reply-To: <20091204104616.GC1931@jolsa.lab.eng.brq.redhat.com>
On Fri, Dec 04, 2009 at 11:46:16AM +0100, Jiri Olsa wrote:
> > sure, but it is not the trace_seq structure that overflows, it is the bare
> > seq_file underneath. The s_show calls "trace_print_seq":
> >
> > void trace_print_seq(struct seq_file *m, struct trace_seq *s)
> > {
> > int len = s->len >= PAGE_SIZE ? PAGE_SIZE - 1 : s->len;
> >
> > seq_write(m, s->buffer, len);
> >
> > trace_seq_init(s);
> > }
> >
> > it flushes the trace_seq to the seq_file and reinits the trace_seq.
> > But the seq_file will get filled in the end, ending up with
> > not displayed output in that case I described in the first email.
> >
>
> hi, any feedback on this?
>
> thanks,
> jirka
Steven has done some tests and it looks like you were right, the
problem comes from the seq_file, not the trace_seq.
Steve, any news about it?
Thanks.
next prev parent reply other threads:[~2009-12-07 20:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 12:57 Jiri Olsa
2009-11-24 17:14 ` Steven Rostedt
2009-11-24 21:14 ` Frederic Weisbecker
2009-11-24 22:17 ` Frederic Weisbecker
2009-11-24 22:26 ` Steven Rostedt
2009-11-24 22:53 ` Frederic Weisbecker
2009-11-24 23:21 ` Steven Rostedt
2009-11-25 8:47 ` Jiri Olsa
2009-11-25 8:45 ` Jiri Olsa
2009-11-25 16:21 ` Steven Rostedt
2009-12-04 10:46 ` Jiri Olsa
2009-12-07 20:21 ` Frederic Weisbecker [this message]
2009-12-07 20:26 ` Steven Rostedt
2009-12-07 20:33 ` Jiri Olsa
2009-12-10 7:49 ` [tip:tracing/core] tracing: Fix function graph trace_pipe " tip-bot for Jiri Olsa
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=20091207202146.GE5049@nowhere \
--to=fweisbec@gmail.com \
--cc=jolsa@redhat.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
Powered by JetHome