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/2] tracing: Fixes for 6-6-rc2
Date: Sat, 23 Sep 2023 18:33:31 -0400 [thread overview]
Message-ID: <20230923223331.720351929@goodmis.org> (raw)
Tracing fixes for 6.6-rc2:
- Fix the "bytes" output of the per_cpu stat file
The tracefs/per_cpu/cpu*/stats "bytes" was giving bogus values as the
accounting was not accurate. It is suppose to show how many used bytes are
still in the ring buffer, but even when the ring buffer was empty it would
still show there were bytes used.
- Fix a bug in eventfs where reading a dynamic event directory (open) and then
creating a dynamic event that goes into that diretory screws up the accounting.
On close, the newly created event dentry will get a "dput" without ever having
a "dget" done for it. The fix is to allocate an array on dir open to save what
dentries were actually "dget" on, and what ones to "dput" on close.
Please pull the latest trace/urgent tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/urgent
Head SHA1: ef36b4f92868d66908e235980f74afdfb9742d12
Steven Rostedt (Google) (1):
eventfs: Remember what dentries were created on dir open
Zheng Yejian (1):
ring-buffer: Fix bytes info in per_cpu buffer stats
----
fs/tracefs/event_inode.c | 87 +++++++++++++++++++++++++++++++++++++---------
kernel/trace/ring_buffer.c | 28 ++++++++-------
2 files changed, 85 insertions(+), 30 deletions(-)
next reply other threads:[~2023-09-23 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 22:33 Steven Rostedt [this message]
2023-09-23 22:33 ` [for-linus][PATCH 1/2] ring-buffer: Fix bytes info in per_cpu buffer stats Steven Rostedt
2023-09-23 22:33 ` [for-linus][PATCH 2/2] eventfs: Remember what dentries were created on dir open 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=20230923223331.720351929@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