From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/5] tracing: Fixes for v6.3
Date: Tue, 14 Mar 2023 15:02:36 -0400 [thread overview]
Message-ID: <20230314190236.203370742@goodmis.org> (raw)
Arnd Bergmann (1):
ftrace,kcfi: Define ftrace_stub_graph conditionally
Chen Zhongjin (1):
ftrace: Fix invalid address access in lookup_rec() when index is 0
Steven Rostedt (Google) (3):
tracing: Do not let histogram values have some modifiers
tracing: Check field value in hist_field_name()
tracing: Make tracepoint lockdep check actually test something
----
arch/x86/kernel/ftrace_64.S | 2 ++
include/linux/tracepoint.h | 15 ++++++---------
kernel/trace/ftrace.c | 3 ++-
kernel/trace/trace_events_hist.c | 12 ++++++++++++
4 files changed, 22 insertions(+), 10 deletions(-)
next reply other threads:[~2023-03-14 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 19:02 Steven Rostedt [this message]
2023-03-14 19:02 ` [for-linus][PATCH 1/5] tracing: Do not let histogram values have some modifiers Steven Rostedt
2023-03-14 19:02 ` [for-linus][PATCH 2/5] tracing: Check field value in hist_field_name() Steven Rostedt
2023-03-14 19:02 ` [for-linus][PATCH 3/5] ftrace: Fix invalid address access in lookup_rec() when index is 0 Steven Rostedt
2023-03-14 19:02 ` [for-linus][PATCH 4/5] ftrace,kcfi: Define ftrace_stub_graph conditionally Steven Rostedt
2023-03-14 19:02 ` [for-linus][PATCH 5/5] tracing: Make tracepoint lockdep check actually test something Steven Rostedt
2023-03-14 21:08 ` Paul E. McKenney
2023-03-14 21:49 ` Steven Rostedt
2023-03-14 23:03 ` Joel Fernandes
2023-03-14 23:07 ` Joel Fernandes
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=20230314190236.203370742@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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