From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] ring-buffer: Fix refcount setting of boot mapped buffers
Date: Sat, 12 Oct 2024 14:20:54 +0900 [thread overview]
Message-ID: <20241012142054.bc1fffb7b4829ff2e496e566@kernel.org> (raw)
In-Reply-To: <20241011165224.33dd2624@gandalf.local.home>
On Fri, 11 Oct 2024 16:52:24 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> A ring buffer which has its buffered mapped at boot up to fixed memory
> should not be freed. Other buffers can be. The ref counting setup was
> wrong for both. It made the not mapped buffers ref count have zero, and the
> boot mapped buffer a ref count of 1. But an normally allocated buffer
> should be 1, where it can be removed.
>
> Keep the ref count of a normal boot buffer with its setup ref count (do
> not decrement it), and increment the fixed memory boot mapped buffer's ref
> count.
>
Looks good to me.
Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you,
> Fixes: e645535a954ad ("tracing: Add option to use memmapped memory for trace boot instance")
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> kernel/trace/trace.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index c01375adc471..5ba40f39c8b5 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -10610,10 +10610,10 @@ __init static void enable_instances(void)
> * cannot be deleted by user space, so keep the reference
> * to it.
> */
> - if (start)
> + if (start) {
> tr->flags |= TRACE_ARRAY_FL_BOOT;
> - else
> - trace_array_put(tr);
> + tr->ref++;
> + }
>
> while ((tok = strsep(&curr_str, ","))) {
> early_enable_events(tr, tok, true);
> --
> 2.45.2
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2024-10-12 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 20:52 [PATCH] ring-buffer: Fix refcount setting of boot mapped buffers Steven Rostedt
2024-10-12 5:20 ` Masami Hiramatsu [this message]
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=20241012142054.bc1fffb7b4829ff2e496e566@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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