From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] [GIT PULL][v3.9-rc7] tracing: Another fix by Namhyung
Date: Fri, 12 Apr 2013 21:01:21 -0400 [thread overview]
Message-ID: <20130413010121.658707789@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
Linus,
Namhyung found and fixed another nasty bug, where you can crash the
kernel with: echo 1234 | tee -a /sys/kernel/debug/tracing/set_ftrace_pid
Luckily, only root has permissions to write to that file.
I also added a fix on top of Namhyung's as his patch added a reference
outside of the DYNAMIC_FTRACE to a function that is only defined
in DYNAMIC_FTRACE. This fixes compiling with FUNCTION_TRACING and
without DYNAMIC_FTRACE (although I don't know who does that anymore).
-- Steve
Please pull the latest trace-fixes-v3.9-rc-v3 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-fixes-v3.9-rc-v3
Head SHA1: 0e1bb617b40659414778baf3203c2ea0dcda1ca7
Namhyung Kim (1):
tracing: Fix possible NULL pointer dereferences
Steven Rostedt (Red Hat) (1):
ftrace: Move ftrace_filter_lseek out of CONFIG_DYNAMIC_FTRACE section
----
include/linux/ftrace.h | 3 ++-
kernel/trace/ftrace.c | 36 ++++++++++++++++++------------------
kernel/trace/trace_stack.c | 2 +-
3 files changed, 21 insertions(+), 20 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2013-04-13 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 1:01 Steven Rostedt [this message]
2013-04-13 1:01 ` [PATCH 1/2] tracing: Fix possible NULL pointer dereferences Steven Rostedt
2013-04-13 1:01 ` [PATCH 2/2] ftrace: Move ftrace_filter_lseek out of CONFIG_DYNAMIC_FTRACE section 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=20130413010121.658707789@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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