From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: [PATCH 0/4] tracing: Cleanup uprobe/eprobe events
Date: Wed, 13 Aug 2025 23:29:36 +0900 [thread overview]
Message-ID: <175509537667.193596.9139462012987606126.stgit@devnote2> (raw)
Hi,
This series is just for cleanup ugly gotos in uprobe/eprobe events
using __free(). Also, this allocates the traceprobe_parse_context
outside of the argument parsing loop for efficiency.
Thank you,
---
Masami Hiramatsu (Google) (4):
tracing: probes: Use __free() for trace_probe_log
tracing: eprobe: Cleanup eprobe event using __free()
tracing: uprobes: Cleanup __trace_uprobe_create() with __free()
tracing: uprobe: eprobes: Allocate traceprobe_parse_context per probe
kernel/trace/trace_eprobe.c | 108 ++++++++++++++++++-------------------------
kernel/trace/trace_probe.c | 3 +
kernel/trace/trace_probe.h | 4 +-
kernel/trace/trace_uprobe.c | 82 +++++++++++++--------------------
4 files changed, 81 insertions(+), 116 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2025-08-13 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 14:29 Masami Hiramatsu (Google) [this message]
2025-08-13 14:29 ` [PATCH 1/4] tracing: probes: Use __free() for trace_probe_log Masami Hiramatsu (Google)
2025-08-13 14:29 ` [PATCH 2/4] tracing: eprobe: Cleanup eprobe event using __free() Masami Hiramatsu (Google)
2025-08-13 14:30 ` [PATCH 3/4] tracing: uprobes: Cleanup __trace_uprobe_create() with __free() Masami Hiramatsu (Google)
2025-08-13 14:30 ` [PATCH 4/4] tracing: uprobe: eprobes: Allocate traceprobe_parse_context per probe Masami Hiramatsu (Google)
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=175509537667.193596.9139462012987606126.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.