public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/4] tracing: Remove the backup instance automatically after read
Date: Fri, 30 Jan 2026 18:24:09 +0900	[thread overview]
Message-ID: <20260130182409.3e5b9f86dcfe7625b3b582cd@kernel.org> (raw)
In-Reply-To: <20260129151352.12e2be72@gandalf.local.home>

On Thu, 29 Jan 2026 15:13:52 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Wed, 28 Jan 2026 09:10:04 +0900
> "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> 
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > 
> > Since the backup instance is readonly, after reading all data
> > via pipe, no data is left on the instance. Thus it can be
> > removed safely after closing all files.
> > This also removes it if user resets the ring buffer manually
> > via 'trace' file.
> > 
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > ---
> >  Changes in v4:
> >    - Update description.
> > ---
> >  kernel/trace/trace.c |   64 +++++++++++++++++++++++++++++++++++++++++++++++++-
> >  kernel/trace/trace.h |    6 +++++
> >  2 files changed, 69 insertions(+), 1 deletion(-)
> > 
> > diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> > index d39f6509c12a..7d615a74f915 100644
> > --- a/kernel/trace/trace.c
> > +++ b/kernel/trace/trace.c
> > @@ -590,6 +590,55 @@ void trace_set_ring_buffer_expanded(struct trace_array *tr)
> >  	tr->ring_buffer_expanded = true;
> >  }
> >  
> > +static int __remove_instance(struct trace_array *tr);
> > +
> > +static void trace_array_autoremove(struct work_struct *work)
> > +{
> > +	struct trace_array *tr = container_of(work, struct trace_array, autoremove_work);
> > +
> > +	guard(mutex)(&event_mutex);
> > +	guard(mutex)(&trace_types_lock);
> > +
> > +	/*
> > +	 * This can be fail if someone gets @tr before starting this
> > +	 * function, but in that case, this will be kicked again when
> > +	 * putting it. So we don't care the result.
> 
> 			"So we don't care about the result."

OK.

> 
> > +	 */
> > +	__remove_instance(tr);
> > +}
> > +
> > +static struct workqueue_struct *autoremove_wq;
> > +
> > +static void trace_array_init_autoremove(struct trace_array *tr)
> > +{
> > +	INIT_WORK(&tr->autoremove_work, trace_array_autoremove);
> > +}
> > +
> > +static void trace_array_kick_autoremove(struct trace_array *tr)
> > +{
> > +	if (!work_pending(&tr->autoremove_work) && autoremove_wq)
> > +		queue_work(autoremove_wq, &tr->autoremove_work);
> > +}
> > +
> > +static void trace_array_cancel_autoremove(struct trace_array *tr)
> > +{
> > +	if (work_pending(&tr->autoremove_work))
> > +		cancel_work(&tr->autoremove_work);
> > +}
> > +
> > +__init static int trace_array_init_autoremove_wq(void)
> > +{
> 
> This isn't needed if there's no backup trace_array right?
> 
> Instead of creating a work queue when its not needed, just exit out if
> there's no backup trace_array.
> 
> Oh, and the above functions should always test autoremove_wq for NULL.

Ah, right. OK, let me fix it.

> 
> > +	autoremove_wq = alloc_workqueue("tr_autoremove_wq",
> > +					WQ_UNBOUND | WQ_HIGHPRI, 0);
> > +	if (!autoremove_wq) {
> > +		pr_err("Unable to allocate tr_autoremove_wq\n");
> > +		return -ENOMEM;
> > +	}
> > +	return 0;
> > +}
> > +
> > +late_initcall_sync(trace_array_init_autoremove_wq);
> > +
> >  LIST_HEAD(ftrace_trace_arrays);
> >  
> >  int trace_array_get(struct trace_array *this_tr)
> > @@ -598,7 +647,7 @@ int trace_array_get(struct trace_array *this_tr)
> >  
> >  	guard(mutex)(&trace_types_lock);
> >  	list_for_each_entry(tr, &ftrace_trace_arrays, list) {
> > -		if (tr == this_tr) {
> > +		if (tr == this_tr && !tr->free_on_close) {
> >  			tr->ref++;
> >  			return 0;
> >  		}
> 
> Break the above into:
> 
> 		if (tr == this_tr) {
> 			if (tr->free_on_close)
> 				break;
> 			tr->ref++;
> 			return 0;
> 		}
> 
> Why continue the loop if we found the trace_array but it's in the process
> of closing?

Ah, indeed. OK, I'll fix it.

Thank you!

> 
> -- Steve
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2026-01-30  9:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28  0:09 [PATCH v5 0/4] tracing: Remove backup instance after read all Masami Hiramatsu (Google)
2026-01-28  0:09 ` [PATCH v5 1/4] tracing: Reset last_boot_info if ring buffer is reset Masami Hiramatsu (Google)
2026-01-28  0:09 ` [PATCH v5 2/4] tracing: Make the backup instance non-reusable Masami Hiramatsu (Google)
2026-01-29 19:53   ` Steven Rostedt
2026-01-30  9:01     ` Masami Hiramatsu
2026-01-29 20:07   ` Steven Rostedt
2026-01-30  9:20     ` Masami Hiramatsu
2026-01-30 15:21       ` Steven Rostedt
2026-01-28  0:10 ` [PATCH v5 3/4] tracing: Remove the backup instance automatically after read Masami Hiramatsu (Google)
2026-01-29 20:13   ` Steven Rostedt
2026-01-30  9:24     ` Masami Hiramatsu [this message]
2026-01-28  0:10 ` [PATCH v5 4/4] tracing/Documentation: Add a section about backup instance Masami Hiramatsu (Google)
2026-01-29 20:19   ` Steven Rostedt
2026-01-30 13:24     ` Masami Hiramatsu
2026-01-30 14:23       ` Steven Rostedt
2026-01-30 14:27         ` 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=20260130182409.3e5b9f86dcfe7625b3b582cd@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