[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <174343532655.843280.15317319860632975273.stgit@devnote2>
Date: Tue, 1 Apr 2025 00:35:26 +0900
From: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org
Subject: [PATCH v2 0/7] tracing: fprobe-events: Register fprobe only when the event is enabled
Hi,
Here is the 2nd version of the series to register fprobe only when the
fprobe event is enabled. The previous version is here;
https://lore.kernel.org/all/174212767109.348872.18231451508464729427.stgit@devnote2/
In this version, I added fixes([1/7] and [2/7]) related to module
unloading ([1/7] should be handled separatedly) and updates
according to the previous thread.
Steve suggested the fprobe-events are always registered when it is
defined, even if it is disabled and that makes system overhead.
This series registeres the fprobes only when the event is enabled.
Thank you,
---
Masami Hiramatsu (Google) (7):
tracing: fprobe events: Fix possible UAF on modules
tracing: fprobe: Cleanup fprobe hash when module unloading
tracing: tprobe-events: Remove mod field from tprobe-event
tracing: tprobe-events: Support multiple tprobes on the same tracepoint
tracing: fprobe-events: Register fprobe-events only when it is enabled
selftests: tracing: Enable fprobe events before checking enable_functions
tracing: tprobe-events: Register tracepoint when enable tprobe event
include/linux/fprobe.h | 5
include/linux/module.h | 4
kernel/trace/fprobe.c | 108 ++++
kernel/trace/trace_fprobe.c | 593 +++++++++++++-------
.../ftrace/test.d/dynevent/add_remove_fprobe.tc | 30 +
5 files changed, 531 insertions(+), 209 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists