From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: [PATCH 0/2] [GIT PULL][v3.1] kprobes: can cause perf to crash the system
Date: Mon, 10 Oct 2011 15:17:06 -0400 [thread overview]
Message-ID: <20111010191706.044816068@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
Ingo,
I tested and verified that the commends that Masami has shown will
crash the system. These patches do fix the problem.
I also verified that the same commands will crash 2.6.39 and have included
stable in the Cc of the commits.
-- Steve
Please pull the latest tip/perf/urgent tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/urgent
Head SHA1: 44a56040a0037a845d5fa218dffde464579f0cab
Masami Hiramatsu (2):
ftrace/kprobes: Fix not to delete probes if in use
perf probe: Fix to show correct error string
----
kernel/trace/trace_kprobe.c | 58 ++++++++++++++++++++++++++++++++++------
tools/perf/util/probe-event.c | 4 ++-
2 files changed, 52 insertions(+), 10 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-10-10 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 19:17 Steven Rostedt [this message]
2011-10-10 19:17 ` [PATCH 1/2] ftrace/kprobes: Fix not to delete probes if in use Steven Rostedt
2011-10-10 19:17 ` [PATCH 2/2] perf probe: Fix to show correct error string Steven Rostedt
2011-10-12 7:08 ` [PATCH 0/2] [GIT PULL][v3.1] kprobes: can cause perf to crash the system 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=20111010191706.044816068@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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