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] tracing: Last minute fixes for 4.12
Date: Fri, 30 Jun 2017 18:04:02 -0400 [thread overview]
Message-ID: <20170630220402.465621079@goodmis.org> (raw)
Linus,
Two fixes:
One is for a crash when using the :mod: trace probe command into
stack_trace_filter. This bug was introduced during the last merge
window.
The other was there forever. It's a small bug that makes it impossible
to name a module function for kprobes when the module starts with a digit.
Please pull the latest trace-v4.12-rc5 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.12-rc5
Tag SHA1: 223396dc4638984b67e90dc89df5a889b8768e8e
Head SHA1: 9e52b32567126fe146f198971364f68d3bc5233f
Sabrina Dubroca (1):
tracing/kprobes: Allow to create probe with a module name starting with a digit
Steven Rostedt (VMware) (1):
ftrace: Fix regression with module command in stack_trace_filter
----
kernel/trace/ftrace.c | 3 ---
kernel/trace/trace.c | 3 +++
kernel/trace/trace_functions.c | 12 ++++++++++++
kernel/trace/trace_kprobe.c | 14 +++++---------
kernel/trace/trace_stack.c | 6 ++++--
5 files changed, 24 insertions(+), 14 deletions(-)
next reply other threads:[~2017-06-30 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 22:04 Steven Rostedt [this message]
2017-06-30 22:04 ` [PATCH 1/2] ftrace: Fix regression with module command in stack_trace_filter Steven Rostedt
2017-06-30 22:04 ` [PATCH 2/2] tracing/kprobes: Allow to create probe with a module name starting with a digit 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=20170630220402.465621079@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
Powered by JetHome