From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/4] [GIT PULL] tracing: real fix for set_ftrace_filter
Date: Tue, 14 Sep 2010 16:27:14 -0400 [thread overview]
Message-ID: <20100914202714.376849326@goodmis.org> (raw)
Ingo,
This includes the real fix for the bug that was found for
set_ftrace_filter. Since I noticed that Linus's tree has the
quick fix that Christ Wright and I made, I just based off of
mainline.
-- Steve
Please pull the latest tip/perf/core tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/perf/core
Steven Rostedt (4):
tracing: Do not reset *pos in set_ftrace_filter
tracing: Replace typecasted void pointer in set_ftrace_filter code
tracing: Keep track of set_ftrace_filter position and allow lseek again
tracing: Fix reading of set_ftrace_filter across lists
----
kernel/trace/ftrace.c | 105 +++++++++++++++++++++++++++++++++++-------------
1 files changed, 76 insertions(+), 29 deletions(-)
next reply other threads:[~2010-09-14 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 20:27 Steven Rostedt [this message]
2010-09-14 20:27 ` [PATCH 1/4] tracing: Do not reset *pos in set_ftrace_filter Steven Rostedt
2010-09-14 20:27 ` [PATCH 2/4] tracing: Replace typecasted void pointer in set_ftrace_filter code Steven Rostedt
2010-09-14 20:27 ` [PATCH 3/4] tracing: Keep track of set_ftrace_filter position and allow lseek again Steven Rostedt
2010-09-14 20:27 ` [PATCH 4/4] tracing: Fix reading of set_ftrace_filter across lists Steven Rostedt
2010-09-15 8:28 ` [PATCH 0/4] [GIT PULL] tracing: real fix for set_ftrace_filter Ingo Molnar
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=20100914202714.376849326@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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