From: Steven Rostedt <rostedt@kernel.org>
To: linux-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>,
Tomas Glozar <tglozar@redhat.com>, John Kacur <jkacur@redhat.com>
Subject: [for-linus][PATCH 0/3] tracing: Fixes for v6.18
Date: Fri, 07 Nov 2025 08:07:30 -0500 [thread overview]
Message-ID: <20251107130730.158197641@kernel.org> (raw)
Fixes for tracing:
- Check for reader catching up in ring_buffer_map_get_reader()
If the reader catches up to the writer in the memory mapped ring buffer
then calling rb_get_reader_page() will return NULL as there's no
pages left. But this isn't checked for before calling rb_get_reader_page()
and the return of NULL causes a warning.
If it is detected that the reader caught up to the writer, then simply
exit the routine.
- Fix memory leak in histogram create_field_var()
The couple of the error paths in create_field_var() did not properly clean
up what was allocated. Make sure everything is freed properly on error.
- Fix help message of tools latency_collector
The help message incorrectly stated that "-t" was the same as "--threads"
whereas "--threads" is actually represented by "-e".
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/fixes
Head SHA1: 53afec2c8fb2a562222948cb1c2aac48598578c9
Steven Rostedt (1):
ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up
Zhang Chujun (1):
tracing/tools: Fix incorrcet short option in usage text for --threads
Zilin Guan (1):
tracing: Fix memory leaks in create_field_var()
----
kernel/trace/ring_buffer.c | 4 ++++
kernel/trace/trace_events_hist.c | 6 ++++--
tools/tracing/latency/latency-collector.c | 2 +-
3 files changed, 9 insertions(+), 3 deletions(-)
next reply other threads:[~2025-11-07 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 13:07 Steven Rostedt [this message]
2025-11-07 13:07 ` [for-linus][PATCH 1/3] ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up Steven Rostedt
2025-11-07 13:07 ` [for-linus][PATCH 2/3] tracing: Fix memory leaks in create_field_var() Steven Rostedt
2025-11-07 13:07 ` [for-linus][PATCH 3/3] tracing/tools: Fix incorrcet short option in usage text for --threads Steven Rostedt
2025-11-07 13:37 ` Mathieu Desnoyers
2025-11-07 17:36 ` 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=20251107130730.158197641@kernel.org \
--to=rostedt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=tglozar@redhat.com \
/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.