From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/7] tracing: Fixes for 5.2-rc4
Date: Sat, 15 Jun 2019 08:42:16 -0400 [thread overview]
Message-ID: <20190615124216.188179157@goodmis.org> (raw)
This is the queue for my next pull request to Linus.
Eiichi Tsukata (3):
tracing: Fix out-of-range read in trace_stack_print()
tracing/uprobe: Fix NULL pointer dereference in trace_uprobe_create()
tracing/uprobe: Fix obsolete comment on trace_uprobe_create()
Josh Poimboeuf (1):
module: Fix livepatch/ftrace module text permissions race
Vasily Gorbik (1):
tracing: avoid build warning with HAVE_NOP_MCOUNT
Wei Li (1):
ftrace: Fix NULL pointer dereference in free_ftrace_func_mapper()
YueHaibing (1):
tracing: Make two symbols static
----
kernel/livepatch/core.c | 6 ++++++
kernel/trace/ftrace.c | 22 ++++++++++++++++------
kernel/trace/trace.c | 4 ++--
kernel/trace/trace_output.c | 2 +-
kernel/trace/trace_uprobe.c | 15 ++++++++++-----
5 files changed, 35 insertions(+), 14 deletions(-)
next reply other threads:[~2019-06-15 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 12:42 Steven Rostedt [this message]
2019-06-15 12:42 ` [for-linus][PATCH 1/7] tracing: Fix out-of-range read in trace_stack_print() Steven Rostedt
2019-06-15 12:42 ` [for-linus][PATCH 3/7] tracing: Make two symbols static Steven Rostedt
2019-06-15 12:42 ` [for-linus][PATCH 4/7] tracing/uprobe: Fix NULL pointer dereference in trace_uprobe_create() Steven Rostedt
2019-06-15 12:42 ` [for-linus][PATCH 5/7] tracing/uprobe: Fix obsolete comment on trace_uprobe_create() Steven Rostedt
2019-06-15 12:42 ` [for-linus][PATCH 6/7] module: Fix livepatch/ftrace module text permissions race Steven Rostedt
2019-06-15 12:42 ` [for-linus][PATCH 7/7] ftrace: Fix NULL pointer dereference in free_ftrace_func_mapper() 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=20190615124216.188179157@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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