From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/7] tracing: A few more fixes for 6.5
Date: Sat, 29 Jul 2023 14:33:33 -0400 [thread overview]
Message-ID: <20230729183333.357029101@goodmis.org> (raw)
Tracing fixes for 6.5:
- Fix to /sys/kernel/tracing/per_cpu/cpu*/stats read and entries.
If a resize shrinks the buffer it clears the read count to notify
readers that they need to reset. But the read count is also used for
accounting and this causes the numbers to be off. Instead, create a
separate variable to use to notify readers to reset.
- Fix the ref counts of the "soft disable" mode. The wrong value was
used for testing if soft disable mode should be enabled or disable,
but instead, just change the logic to do the enable and disable
in place when the SOFT_MODE is set or cleared.
- Several kernel-doc fixes
- Removal of unused external declarations
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/urgent
Head SHA1: dea499781a1150d285c62b26659f62fb00824fce
Gaosheng Cui (4):
ring-buffer: Fix kernel-doc warnings in ring_buffer.c
tracing/synthetic: Fix kernel-doc warnings in trace_events_synth.c
tracing: Fix kernel-doc warnings in trace_events_trigger.c
tracing: Fix kernel-doc warnings in trace_seq.c
YueHaibing (1):
ftrace: Remove unused extern declarations
Zheng Yejian (2):
ring-buffer: Fix wrong stat of cpu_buffer->read
tracing: Fix warning in trace_buffered_event_disable()
----
include/linux/ftrace.h | 4 ----
kernel/trace/ring_buffer.c | 25 +++++++++++++------------
kernel/trace/trace_events.c | 14 ++++----------
kernel/trace/trace_events_synth.c | 1 +
kernel/trace/trace_events_trigger.c | 2 ++
kernel/trace/trace_seq.c | 1 +
6 files changed, 21 insertions(+), 26 deletions(-)
next reply other threads:[~2023-07-29 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 18:33 Steven Rostedt [this message]
2023-07-29 18:33 ` [for-linus][PATCH 1/7] ring-buffer: Fix wrong stat of cpu_buffer->read Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 2/7] ring-buffer: Fix kernel-doc warnings in ring_buffer.c Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 3/7] tracing/synthetic: Fix kernel-doc warnings in trace_events_synth.c Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 4/7] tracing: Fix kernel-doc warnings in trace_events_trigger.c Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 5/7] tracing: Fix kernel-doc warnings in trace_seq.c Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 6/7] ftrace: Remove unused extern declarations Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 7/7] tracing: Fix warning in trace_buffered_event_disable() 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=20230729183333.357029101@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox