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-next][PATCH 0/6] tracing: A few updates for 4.16
Date: Wed, 24 Jan 2018 13:36:33 -0500 [thread overview]
Message-ID: <20180124183633.610217564@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 841a915d20c7b22fc4f36f12368daf94d9f8cb10
Andi Kleen (1):
ftrace: Mark function tracer test functions noinline/noclone
Changbin Du (3):
tracing: Detect the string nul character when parsing user input string
tracing: Clear parser->idx if only spaces are read
tracing: Make sure the parsed string always terminates with '\0'
Ravi Bangoria (1):
trace_uprobe: Display correct offset in uprobe_events
Steven Rostedt (VMware) (1):
vsprintf: Do not have bprintf dereference pointers
----
kernel/trace/ftrace.c | 2 -
kernel/trace/trace.c | 14 +++---
kernel/trace/trace_events.c | 2 -
kernel/trace/trace_selftest_dynamic.c | 5 ++-
kernel/trace/trace_uprobe.c | 2 +-
lib/vsprintf.c | 82 +++++++++++++++++++++++++++++------
6 files changed, 80 insertions(+), 27 deletions(-)
next reply other threads:[~2018-01-24 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 18:36 Steven Rostedt [this message]
2018-01-24 18:36 ` [for-next][PATCH 1/6] tracing: Detect the string nul character when parsing user input string Steven Rostedt
2018-01-24 18:36 ` [for-next][PATCH 2/6] tracing: Clear parser->idx if only spaces are read Steven Rostedt
2018-01-24 18:36 ` [for-next][PATCH 3/6] tracing: Make sure the parsed string always terminates with \0 Steven Rostedt
2018-01-24 18:36 ` [for-next][PATCH 4/6] trace_uprobe: Display correct offset in uprobe_events Steven Rostedt
2018-01-24 18:36 ` [for-next][PATCH 5/6] ftrace: Mark function tracer test functions noinline/noclone Steven Rostedt
2018-01-24 18:36 ` [for-next][PATCH 6/6] vsprintf: Do not have bprintf dereference pointers 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=20180124183633.610217564@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
Powered by JetHome