From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Zhaolei <zhaolei@cn.fujitsu.com>,
Tom Zanussi <tzanussi@gmail.com>, Li Zefan <lizf@cn.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] tracing: recursion protection fixes
Date: Mon, 20 Apr 2009 10:47:29 +0200 [thread overview]
Message-ID: <20090420084729.GB32625@elte.hu> (raw)
In-Reply-To: <1240178868-18218-1-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Hi,
>
> Here are two fixes for tracing recursion protection.
> The first slightly improves debugging in case of recursion detection.
> The second fixes a spurious warning and tracing disabling while
> activating a filter.
>
> The following changes since commit 8e668b5b3455207e4540fc7ccab9ecf70142f288:
> Steven Rostedt (1):
> tracing: remove format attribute of inline function
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git tracing/recursion
>
> Frederic Weisbecker (2):
> tracing/core: Add current context on tracing recursion warning
> tracing/ring-buffer: unlock recursion protection on discard
>
> kernel/trace/ring_buffer.c | 25 ++++++++++++++++++++-----
> 1 files changed, 20 insertions(+), 5 deletions(-)
Pulled, thanks Frederic! Steve, any objections?
Ingo
next prev parent reply other threads:[~2009-04-20 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 22:07 Frederic Weisbecker
2009-04-19 22:07 ` [PATCH 1/2 v3] tracing/core: Add current context on tracing recursion warning Frederic Weisbecker
2009-04-19 22:07 ` [PATCH 2/2] tracing/ring-buffer: unlock recursion protection on discard Frederic Weisbecker
2009-04-20 8:47 ` Ingo Molnar [this message]
2009-04-21 22:04 ` [PATCH 0/2] tracing: recursion protection fixes Steven Rostedt
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=20090420084729.GB32625@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®