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 00/10] tracing: Fixes for 6.0
Date: Sat, 20 Aug 2022 20:07:37 -0400 [thread overview]
Message-ID: <20220821000737.328590235@goodmis.org> (raw)
Various fixes for tracing:
- Suppress the errors that is_signed_type() causes static analysis tools
- Fix a return value of traceprobe_parse_event_name()
- Fix NULL pointer dereference from failed ftrace enabling
- Fix NULL pointer dereference by asking for registers from eprobes
- Make eprobes consistent with kprobes/uprobes, filters and histograms
Bart Van Assche (1):
tracing: Suppress sparse warnings triggered by is_signed_type()
Lukas Bulwahn (1):
tracing: React to error return from traceprobe_parse_event_name()
Steven Rostedt (Google) (7):
tracing/perf: Fix double put of trace event when init fails
tracing/eprobes: Do not allow eprobes to use $stack, or % for regs
tracing/eprobes: Do not hardcode $comm as a string
tracing/eprobes: Fix reading of string fields
tracing/eprobes: Have event probes be consistent with kprobes and uprobes
tracing/probes: Have kprobes and uprobes use $COMM too
tracing: Have filter accept "common_cpu" to be consistent
Yang Jihong (1):
ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead
----
include/linux/trace_events.h | 12 ++++++
kernel/trace/ftrace.c | 10 +++++
kernel/trace/trace_eprobe.c | 93 +++++++++++++++++++++++++++++++++++++----
kernel/trace/trace_event_perf.c | 7 ++--
kernel/trace/trace_events.c | 1 +
kernel/trace/trace_probe.c | 29 ++++++++-----
6 files changed, 131 insertions(+), 21 deletions(-)
next reply other threads:[~2022-08-21 0:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 0:07 Steven Rostedt [this message]
2022-08-21 0:07 ` [for-linus][PATCH 01/10] tracing: Suppress sparse warnings triggered by is_signed_type() Steven Rostedt
2022-08-21 18:35 ` Linus Torvalds
2022-08-21 19:55 ` Steven Rostedt
2022-08-22 18:20 ` Bart Van Assche
2022-08-22 18:45 ` Linus Torvalds
2022-08-22 20:19 ` Bart Van Assche
2022-08-23 7:06 ` Rasmus Villemoes
2022-08-23 22:05 ` Bart Van Assche
2022-08-23 23:18 ` Linus Torvalds
2022-08-23 23:57 ` Linus Torvalds
2022-08-24 2:09 ` Al Viro
2022-08-24 2:16 ` Linus Torvalds
2022-08-24 3:10 ` Al Viro
2022-08-24 3:20 ` Al Viro
2022-08-24 5:56 ` Linus Torvalds
2022-08-24 0:09 ` Bart Van Assche
2022-08-24 1:49 ` Linus Torvalds
2022-08-24 2:11 ` Linus Torvalds
2022-08-24 3:47 ` Bart Van Assche
2022-08-24 3:46 ` Bart Van Assche
2022-08-24 23:28 ` Bart Van Assche
2022-08-25 0:30 ` Linus Torvalds
2022-08-25 0:40 ` Linus Torvalds
2022-08-25 7:57 ` Rasmus Villemoes
2022-08-25 8:07 ` Linus Torvalds
2022-08-25 17:39 ` Bart Van Assche
2022-08-25 18:17 ` Kees Cook
2022-08-21 0:07 ` [for-linus][PATCH 02/10] tracing: React to error return from traceprobe_parse_event_name() Steven Rostedt
2022-08-21 0:07 ` [for-linus][PATCH 03/10] tracing/perf: Fix double put of trace event when init fails Steven Rostedt
2022-08-21 0:07 ` [for-linus][PATCH 04/10] ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead Steven Rostedt
2022-08-21 0:07 ` [for-linus][PATCH 05/10] tracing/eprobes: Do not allow eprobes to use $stack, or % for regs Steven Rostedt
2022-08-21 0:07 ` [for-linus][PATCH 06/10] tracing/eprobes: Do not hardcode $comm as a string Steven Rostedt
2022-08-21 0:07 ` [for-linus][PATCH 07/10] tracing/eprobes: Fix reading of string fields Steven Rostedt
2022-08-21 0:07 ` [for-linus][PATCH 08/10] tracing/eprobes: Have event probes be consistent with kprobes and uprobes Steven Rostedt
2022-08-21 0:07 ` [for-linus][PATCH 09/10] tracing/probes: Have kprobes and uprobes use $COMM too Steven Rostedt
2022-08-21 0:07 ` [for-linus][PATCH 10/10] tracing: Have filter accept "common_cpu" to be consistent 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=20220821000737.328590235@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
all inboxes | Powered by JetHome®