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] tracing: Use refcount for trace_event_file reference counter
Date: Mon, 29 Jul 2024 23:49:24 +0900 [thread overview]
Message-ID: <20240729234924.6accc2e6216e3b7be1a97e61@kernel.org> (raw)
In-Reply-To: <20240726144208.687cce24@rorschach.local.home>
On Fri, 26 Jul 2024 14:42:08 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> Instead of using an atomic counter for the trace_event_file reference
> counter, use the refcount interface. It has various checks to make sure
> the reference counting is correct, and will warn if it detects an error
> (like refcount_inc() on '0').
>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Looks good to me.
Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thanks,
> ---
> include/linux/trace_events.h | 2 +-
> kernel/trace/trace_events.c | 8 ++++----
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/trace_events.h b/include/linux/trace_events.h
> index 9df3e2973626..fed58e54f15e 100644
> --- a/include/linux/trace_events.h
> +++ b/include/linux/trace_events.h
> @@ -680,7 +680,7 @@ struct trace_event_file {
> * caching and such. Which is mostly OK ;-)
> */
> unsigned long flags;
> - atomic_t ref; /* ref count for opened files */
> + refcount_t ref; /* ref count for opened files */
> atomic_t sm_ref; /* soft-mode reference counter */
> atomic_t tm_ref; /* trigger-mode reference counter */
> };
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index 852643d957de..81ade9ddcbe5 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -992,18 +992,18 @@ static void remove_subsystem(struct trace_subsystem_dir *dir)
>
> void event_file_get(struct trace_event_file *file)
> {
> - atomic_inc(&file->ref);
> + refcount_inc(&file->ref);
> }
>
> void event_file_put(struct trace_event_file *file)
> {
> - if (WARN_ON_ONCE(!atomic_read(&file->ref))) {
> + if (WARN_ON_ONCE(!refcount_read(&file->ref))) {
> if (file->flags & EVENT_FILE_FL_FREED)
> kmem_cache_free(file_cachep, file);
> return;
> }
>
> - if (atomic_dec_and_test(&file->ref)) {
> + if (refcount_dec_and_test(&file->ref)) {
> /* Count should only go to zero when it is freed */
> if (WARN_ON_ONCE(!(file->flags & EVENT_FILE_FL_FREED)))
> return;
> @@ -2999,7 +2999,7 @@ trace_create_new_event(struct trace_event_call *call,
> atomic_set(&file->tm_ref, 0);
> INIT_LIST_HEAD(&file->triggers);
> list_add(&file->list, &tr->events);
> - event_file_get(file);
> + refcount_set(&file->ref, 1);
>
> return file;
> }
> --
> 2.43.0
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2024-07-29 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 18:42 [PATCH] tracing: Use refcount for trace_event_file reference counter Steven Rostedt
2024-07-29 14:49 ` Masami Hiramatsu [this message]
2024-07-29 23:02 ` Steven Rostedt
2024-07-30 0:02 ` Masami Hiramatsu
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=20240729234924.6accc2e6216e3b7be1a97e61@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;
as well as URLs for NNTP newsgroup(s).