Linux Trace Kernel
 help / color / mirror / Atom feed
From: Steven Rostedt <steven@rostedt.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: David Carlier <devnexen@gmail.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing: Restore synchronize_rcu() before freeing trigger private data
Date: Thu, 23 Jul 2026 19:21:20 -0400	[thread overview]
Message-ID: <20260723192120.6a556199@gandalf.local.home> (raw)
In-Reply-To: <20260723191846.16a9cec9@gandalf.local.home>


[ Resending with my steven@rostedt.org, as gmail is being a prick ]

On Thu, 23 Jul 2026 19:18:46 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Fri, 24 Jul 2026 06:33:15 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> 
> > Hi David,
> > 
> > Instead of adding just a synchronize_rcu(), can you reconsider to introduce
> > .private_data_free() to event_trigger_data? I hit the same issue on wprobe
> > and fixed it with ".private_free()" (I think private_data_free() is better
> > naming)  
> 
> You mean like this?
> 
>   https://lore.kernel.org/all/20260723191534.67136-1-devnexen@gmail.com/
> 
>   ;-)
> 
> But yeah, David, can you send a v4 that renames private_free() to
> private_data_free()?
> 
> Thanks,
> 
> -- Steve


      reply	other threads:[~2026-07-23 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 17:02 [PATCH v2] tracing: Restore synchronize_rcu() before freeing trigger private data David Carlier
2026-07-23 17:37 ` Steven Rostedt
2026-07-23 21:33 ` Masami Hiramatsu
2026-07-23 23:18   ` Steven Rostedt
2026-07-23 23:21     ` Steven Rostedt [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=20260723192120.6a556199@gandalf.local.home \
    --to=steven@rostedt.org \
    --cc=devnexen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.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