From: Krister Johansen <kjlx@templeofstupid.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
David Reaver <me@davidreaver.com>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 1/1] tracing: fix a WARN from trace_event_dyn_put_ref
Date: Tue, 16 Aug 2022 13:48:43 -0700 [thread overview]
Message-ID: <20220816204843.GB2004@templeofstupid.com> (raw)
In-Reply-To: <20220816152411.086ce631@gandalf.local.home>
On Tue, Aug 16, 2022 at 03:24:11PM -0400, Steven Rostedt wrote:
> Actually, I think the issue is that the unreg() calls trace_event_put_ref()
> but the reg() does not do the try_get_ref(), but the perf_trace_init()
> does. Which is the broken symmetry.
>
> I think if we pull out the trace_event_put_ref() from the unreg() function,
> we fix the bug and also put back the symmetry.
>
> Does this patch work?
Yes, thanks, this change looks correct. It also does build and pass the
tests that I included in the original e-mail.
> diff --git a/kernel/trace/trace_event_perf.c b/kernel/trace/trace_event_perf.c
> index a114549720d6..61e3a2620fa3 100644
> --- a/kernel/trace/trace_event_perf.c
> +++ b/kernel/trace/trace_event_perf.c
> @@ -157,7 +157,7 @@ static void perf_trace_event_unreg(struct perf_event *p_event)
> int i;
>
> if (--tp_event->perf_refcount > 0)
> - goto out;
> + return;
>
> tp_event->class->reg(tp_event, TRACE_REG_PERF_UNREGISTER, NULL);
>
> @@ -176,8 +176,6 @@ static void perf_trace_event_unreg(struct perf_event *p_event)
> perf_trace_buf[i] = NULL;
> }
> }
> -out:
> - trace_event_put_ref(tp_event);
> }
>
> static int perf_trace_event_open(struct perf_event *p_event)
> @@ -241,6 +239,7 @@ void perf_trace_destroy(struct perf_event *p_event)
> mutex_lock(&event_mutex);
> perf_trace_event_close(p_event);
> perf_trace_event_unreg(p_event);
> + trace_event_put_ref(p_event->tp_event);
> mutex_unlock(&event_mutex);
> }
>
> @@ -292,6 +291,7 @@ void perf_kprobe_destroy(struct perf_event *p_event)
> mutex_lock(&event_mutex);
> perf_trace_event_close(p_event);
> perf_trace_event_unreg(p_event);
> + trace_event_put_ref(p_event->tp_event);
> mutex_unlock(&event_mutex);
>
> destroy_local_trace_kprobe(p_event->tp_event);
> @@ -347,6 +347,7 @@ void perf_uprobe_destroy(struct perf_event *p_event)
> mutex_lock(&event_mutex);
> perf_trace_event_close(p_event);
> perf_trace_event_unreg(p_event);
> + trace_event_put_ref(p_event->tp_event);
> mutex_unlock(&event_mutex);
> destroy_local_trace_uprobe(p_event->tp_event);
> }
>
If it matters:
Reviewed-by: Krister Johansen <kjlx@templeofstupid.com>
Tested-by: Krister Johansen <kjlx@templeofstupid.com>
Thanks again,
-K
prev parent reply other threads:[~2022-08-16 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 0:02 [PATCH 0/1] tracing: warn in trace_event_dyn_put_ref Krister Johansen
2022-08-13 0:02 ` [PATCH 1/1] tracing: fix a WARN from trace_event_dyn_put_ref Krister Johansen
2022-08-16 16:25 ` Steven Rostedt
2022-08-16 18:54 ` Krister Johansen
2022-08-16 19:24 ` Steven Rostedt
2022-08-16 20:48 ` Krister Johansen [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=20220816204843.GB2004@templeofstupid.com \
--to=kjlx@templeofstupid.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@davidreaver.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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