From: Nam Cao <namcao@linutronix.de>
To: Gabriele Monaco <gmonaco@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
Nam Cao <namcao@linutronix.de>
Subject: [PATCH v2 0/2] rv: Tidy up with auto-cleanup
Date: Mon, 17 Nov 2025 09:06:01 +0000 [thread overview]
Message-ID: <cover.1763370183.git.namcao@linutronix.de> (raw)
This series tidies up rv code with __free and lock guard. This is motivated
by a bug:
https://lore.kernel.org/all/20250903065112.1878330-1-zhen.ni@easystack.cn/
which was caused by a missing mutex_unlock. This series makes such bug less
likely in the future, and also reduces some code lines.
Nam Cao (2):
rv: Convert to use lock guard
rv: Convert to use __free
kernel/trace/rv/rv.c | 102 +++++++++++++---------------------
kernel/trace/rv/rv.h | 6 +-
kernel/trace/rv/rv_reactors.c | 58 +++++++------------
kernel/trace/trace.c | 3 +-
4 files changed, 66 insertions(+), 103 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-17 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 9:06 Nam Cao [this message]
2025-11-17 9:06 ` [PATCH v2 1/2] rv: Convert to use lock guard Nam Cao
2025-11-25 19:57 ` Steven Rostedt
2025-11-26 7:27 ` Gabriele Monaco
2025-11-26 8:36 ` Nam Cao
2025-11-26 9:33 ` Gabriele Monaco
2025-11-26 15:42 ` Steven Rostedt
2025-11-26 14:51 ` Steven Rostedt
2025-11-26 15:22 ` Gabriele Monaco
2025-12-01 15:24 ` Steven Rostedt
2025-12-01 15:28 ` Gabriele Monaco
2025-12-02 1:38 ` Steven Rostedt
2025-12-02 1:51 ` Steven Rostedt
2025-12-02 6:41 ` Gabriele Monaco
2025-12-01 15:28 ` Nam Cao
2025-11-17 9:06 ` [PATCH v2 2/2] rv: Convert to use __free Nam Cao
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=cover.1763370183.git.namcao@linutronix.de \
--to=namcao@linutronix.de \
--cc=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).