From: Li Zefan <lizf@cn.fujitsu.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
Zhaolei <zhaolei@cn.fujitsu.com>,
Tom Zanussi <tzanussi@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] tracing/core: Add current context on tracing recursion warning
Date: Mon, 20 Apr 2009 08:37:19 +0800 [thread overview]
Message-ID: <49EBC3BF.50404@cn.fujitsu.com> (raw)
In-Reply-To: <20090419172837.GA5992@nowhere>
> Now I can reproduce it. It seems to happen when I set a filter,
Right, you said filter seems to be broken, so I tried to set a filter
and enabled the trace event, and got this warning.
> but also on other situations:
>
> Bisected back to:
>
> commit 261842b7c9099f56de2eb969c8ad65402d68e00e
> tracing: add same level recursion detection
>
> It might be caused by a bug in this patch or
> by real tracing recursions on some places.
prev parent reply other threads:[~2009-04-20 0:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 5:01 [PATCH 0/2 v3] [GIT PULL] tracing/events: add the __string field Frederic Weisbecker
2009-04-19 5:01 ` [PATCH 1/2 v3] tracing/events: provide string with undefined size support Frederic Weisbecker
2009-04-19 6:15 ` Li Zefan
2009-04-19 12:35 ` Frederic Weisbecker
2009-04-21 18:16 ` Frederic Weisbecker
2009-04-21 18:33 ` Steven Rostedt
2009-04-21 21:58 ` Steven Rostedt
2009-04-21 22:00 ` Steven Rostedt
2009-04-21 22:12 ` Frederic Weisbecker
2009-04-21 22:21 ` Steven Rostedt
2009-04-21 23:32 ` [PATCH][GIT-PULL] tracing/events: protect __get_str() Frederic Weisbecker
2009-04-22 10:25 ` Ingo Molnar
2009-04-22 10:41 ` [PATCH 1/2 v3] tracing/events: provide string with undefined size support Ingo Molnar
2009-04-19 5:01 ` [PATCH 2/2 v3] tracing/lock: provide lock_acquired event support for dynamic size string Frederic Weisbecker
2009-04-21 21:59 ` Steven Rostedt
2009-04-19 6:14 ` [PATCH 0/2 v3] [GIT PULL] tracing/events: add the __string field Li Zefan
2009-04-19 12:34 ` Frederic Weisbecker
2009-04-19 13:49 ` [PATCH] tracing/core: Add current context on tracing recursion warning Frederic Weisbecker
2009-04-19 14:01 ` Ingo Molnar
2009-04-19 14:22 ` Frederic Weisbecker
2009-04-19 18:45 ` Ingo Molnar
2009-04-19 18:48 ` Frédéric Weisbecker
2009-04-19 18:47 ` Ingo Molnar
2009-04-19 17:28 ` Frederic Weisbecker
2009-04-20 0:37 ` Li Zefan [this message]
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=49EBC3BF.50404@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
--cc=zhaolei@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 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.