From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH v2 0/5] tracing: Cleanups with use of guard() and __free()
Date: Fri, 01 Aug 2025 16:37:22 -0400 [thread overview]
Message-ID: <20250801203722.072085868@kernel.org> (raw)
This is a cleanup to use guard() and __free() where possible.
Changes since v1: https://lore.kernel.org/linux-trace-kernel/20250801142506.431659758@kernel.org
- Do not use guard(preempt) for trace_event_buffer_lock_reserve() as that
returns with preemption enabled between the disable and enable preempt.
Steven Rostedt (5):
tracing: Remove unneeded goto out logic
tracing: Add guard(ring_buffer_nest)
tracing: Add guard() around locks and mutexes in trace.c
tracing: Use __free(kfree) in trace.c to remove gotos
ring-buffer: Convert ring_buffer_write() to use guard(preempt_notrace)
----
include/linux/ring_buffer.h | 3 +
kernel/trace/ring_buffer.c | 16 +--
kernel/trace/trace.c | 287 ++++++++++++++------------------------
kernel/trace/trace_events_synth.c | 6 +-
kernel/trace/trace_output.c | 17 +--
5 files changed, 114 insertions(+), 215 deletions(-)
next reply other threads:[~2025-08-01 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 20:37 Steven Rostedt [this message]
2025-08-01 20:37 ` [PATCH v2 1/5] tracing: Remove unneeded goto out logic Steven Rostedt
2025-08-01 20:37 ` [PATCH v2 2/5] tracing: Add guard(ring_buffer_nest) Steven Rostedt
2025-08-01 20:37 ` [PATCH v2 3/5] tracing: Add guard() around locks and mutexes in trace.c Steven Rostedt
2025-08-01 20:37 ` [PATCH v2 4/5] tracing: Use __free(kfree) in trace.c to remove gotos Steven Rostedt
2025-08-01 20:37 ` [PATCH v2 5/5] ring-buffer: Convert ring_buffer_write() to use guard(preempt_notrace) 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=20250801203722.072085868@kernel.org \
--to=rostedt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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 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.