From: Steven Rostedt <rostedt@goodmis.org>
To: Henry Martin <bsdhenrymartin@gmail.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
Beau Belgrave <beaub@linux.microsoft.com>
Subject: Re: [PATCH] tracing/user_events: Don't destroy fields when event removal fails
Date: Mon, 24 Aug 2026 16:39:55 -0400 [thread overview]
Message-ID: <20260824163955.522cb5b0@gandalf.local.home> (raw)
In-Reply-To: <20260824102907.4173063-1-bsdhenrymartin@gmail.com>
Beau,
Can you review this patch?
Thanks,
-- Steve
On Mon, 24 Aug 2026 18:29:07 +0800
Henry Martin <bsdhenrymartin@gmail.com> wrote:
> destroy_user_event() destroys the event's fields before attempting to
> remove the trace event call. If user_event_set_call_visible() fails,
> e.g. because the event is still enabled and trace_remove_event_call()
> returns -EBUSY, the event is left registered with an irreversibly
> destroyed field list. Any subsequent interaction with the event then
> operates on an empty field list while it is still fully visible in
> tracefs.
>
> Move the field destruction after the call removal, and splice the
> field list back onto the event when the removal fails so the event
> remains in a consistent state.
>
> Fixes: 7f5a08c79df35 ("user_events: Add minimal support for trace_event into ftrace")
> Signed-off-by: Henry Martin <bsdhenrymartin@gmail.com>
> ---
> kernel/trace/trace_events_user.c | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/trace/trace_events_user.c b/kernel/trace/trace_events_user.c
> index 8c82ecb735f41..0b021c212995a 100644
> --- a/kernel/trace/trace_events_user.c
> +++ b/kernel/trace/trace_events_user.c
> @@ -1119,10 +1119,9 @@ static void user_event_destroy_validators(struct user_event *user)
> }
> }
>
> -static void user_event_destroy_fields(struct user_event *user)
> +static void user_event_destroy_fields(struct list_head *head)
> {
> struct ftrace_event_field *field, *next;
> - struct list_head *head = &user->fields;
>
> list_for_each_entry_safe(field, next, head, link) {
> list_del(&field->link);
> @@ -1499,17 +1498,21 @@ static int user_event_set_call_visible(struct user_event *user, bool visible)
>
> static int destroy_user_event(struct user_event *user)
> {
> + LIST_HEAD(fields);
> int ret = 0;
>
> lockdep_assert_held(&event_mutex);
>
> - /* Must destroy fields before call removal */
> - user_event_destroy_fields(user);
> + list_splice_init(&user->fields, &fields);
>
> ret = user_event_set_call_visible(user, false);
>
> - if (ret)
> + if (ret) {
> + list_splice(&fields, &user->fields);
> return ret;
> + }
> +
> + user_event_destroy_fields(&fields);
>
> dyn_event_remove(&user->devent);
> hash_del(&user->node);
> @@ -2209,7 +2212,7 @@ static int user_event_parse(struct user_event_group *group, char *name,
> put_user_lock:
> mutex_unlock(&event_mutex);
> put_user:
> - user_event_destroy_fields(user);
> + user_event_destroy_fields(&user->fields);
> user_event_destroy_validators(user);
> kfree(user->call.print_fmt);
>
prev parent reply other threads:[~2026-08-24 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 10:29 [PATCH] tracing/user_events: Don't destroy fields when event removal fails Henry Martin
2026-08-24 20:39 ` 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=20260824163955.522cb5b0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=beaub@linux.microsoft.com \
--cc=bsdhenrymartin@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;
as well as URLs for NNTP newsgroup(s).