From: Steven Rostedt <rostedt@goodmis.org>
To: Wesley Atwell <atwellwea@gmail.com>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
mhiramat@kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com, tom.zanussi@linux.intel.com
Subject: Re: [PATCH v4 2/2] tracing: Drain deferred trigger frees if kthread creation fails
Date: Fri, 27 Mar 2026 22:30:22 -0400 [thread overview]
Message-ID: <20260327223022.167defcc@robin> (raw)
In-Reply-To: <CAN=sVvzFMC1m2aGT23aRpPpoddBVP59mQBmEsQyEPKBYm3J_Vw@mail.gmail.com>
On Fri, 27 Mar 2026 16:41:52 -0600
Wesley Atwell <atwellwea@gmail.com> wrote:
> Yes,
>
> This kernel command line reliably reaches trigger_data_free() during boot:
>
> trace_event=sched:sched_switch
> trace_trigger=sched_switch.traceon,sched_switch.traceon
>
> On an unpatched tree, that crashes during early boot before userspace.
> The call trace goes through:
>
> trigger_data_free()
> __kthread_create_on_node()
> try_to_wake_up()
>
> The stack also shows the boot-time trigger registration path:
>
> event_trigger_parse()
> trigger_process_regex()
> __trace_early_add_events()
Thanks for this. I can reproduce the crash. I'm also going to add this
to the change log as it is useful (I'll even add it to one of my
regression tests). I'll take this patch separately (this didn't need to
be a patch series, as the two patches do not depend on each other).
-- Steve
next prev parent reply other threads:[~2026-03-28 2:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 22:13 [PATCH v4 0/2] tracing: Preserve repeated boot-time parameters and drain deferred trigger frees Wesley Atwell
2026-03-24 22:13 ` [PATCH v4 1/2] tracing: Preserve repeated boot-time tracing parameters Wesley Atwell
2026-03-28 17:53 ` Steven Rostedt
2026-03-28 20:18 ` [PATCH v5] " Wesley Atwell
2026-03-24 22:13 ` [PATCH v4 2/2] tracing: Drain deferred trigger frees if kthread creation fails Wesley Atwell
2026-03-27 19:06 ` Steven Rostedt
2026-03-27 22:41 ` Wesley Atwell
2026-03-28 2:30 ` Steven Rostedt [this message]
2026-03-28 4:56 ` Wesley Atwell
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=20260327223022.167defcc@robin \
--to=rostedt@goodmis.org \
--cc=atwellwea@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=tom.zanussi@linux.intel.com \
/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