From: Wesley Atwell <atwellwea@gmail.com>
To: rostedt@goodmis.org
Cc: mhiramat@kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
Wesley Atwell <atwellwea@gmail.com>
Subject: [PATCH v2 0/2] tracing: preserve repeated boot-time parameters and drain deferred trigger frees
Date: Mon, 9 Mar 2026 15:27:00 -0600 [thread overview]
Message-ID: <20260309212702.13622-1-atwellwea@gmail.com> (raw)
Patch 1 preserves repeated tracing boot parameters across the affected
early parsers.
Patch 2 makes deferred trigger-data frees drain correctly if the cleanup
kthread never starts, and restores the review-requested comment context
around the post-mutex recheck and synchronous fallback path.
v2:
- Patch 1: no changes
- Patch 2: restore the dropped mutex recheck comment and clarify the
synchronous fallback drain path
Wesley Atwell (2):
tracing: preserve repeated boot-time tracing parameters
tracing: drain deferred trigger frees if kthread startup fails
kernel/trace/ftrace.c | 29 +++++++++--
kernel/trace/trace.c | 23 ++++++++-
kernel/trace/trace_events.c | 23 +++++++--
kernel/trace/trace_events_trigger.c | 79 ++++++++++++++++++++++++-----
kernel/trace/trace_kprobe.c | 23 ++++++++-
5 files changed, 155 insertions(+), 22 deletions(-)
--
2.34.1
next reply other threads:[~2026-03-09 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 21:27 Wesley Atwell [this message]
2026-03-09 21:27 ` [PATCH v2 1/2] tracing: preserve repeated boot-time tracing parameters Wesley Atwell
2026-03-09 21:27 ` [PATCH v2 2/2] tracing: drain deferred trigger frees if kthread startup fails 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=20260309212702.13622-1-atwellwea@gmail.com \
--to=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.