[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <173289885627.73724.13632317993038475335.stgit@devnote2>
Date: Sat, 30 Nov 2024 01:47:36 +0900
From: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>,
Naveen N Rao <naveen@...nel.org>
Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
"David S . Miller" <davem@...emloft.net>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Oleg Nesterov <oleg@...hat.com>,
Tzvetomir Stoyanov <tz.stoyanov@...il.com>,
linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org
Subject: [PATCH v2 0/6] kprobes: tracing/probes: Fix and cleanup to use guard
Hi,
This is the v2 of the series to fix eprobes and cleanup kprobes and probe
events in ftrace to use guard() and scoped_guard() instead of pairs of mutex
locks.
In this version I fixed mixing of gurad and goto in the same function by
using scoped_guard.
Some locks are still not using guard(). We need some more work to complete.
Thanks,
---
Masami Hiramatsu (Google) (6):
tracing/eprobe: Fix to release eprobe when failed to add dyn_event
kprobes: Adopt guard() and scoped_guard()
tracing/kprobe: Adopt guard() and scoped_guard()
tracing/uprobe: Adopt guard() and scoped_guard()
tracing/eprobe: Adopt guard() and scoped_guard()
tracing/dynevent: Adopt guard() and scoped_guard()
kernel/kprobes.c | 205 ++++++++++++++++++-----------------------
kernel/trace/trace_dynevent.c | 35 +++----
kernel/trace/trace_eprobe.c | 31 +++---
kernel/trace/trace_kprobe.c | 18 +---
kernel/trace/trace_uprobe.c | 15 +--
5 files changed, 133 insertions(+), 171 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists