From: Vincent Donnefort <vdonnefort@google.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v5 16/18] tracing/remotes: Add trace_remote cmdline options
Date: Thu, 13 Aug 2026 15:21:26 +0100 [thread overview]
Message-ID: <an3S5rK5dLZkADSU@google.com> (raw)
In-Reply-To: <20260812171148.D9E9F1F00A3E@smtp.kernel.org>
On Wed, Aug 12, 2026 at 05:11:48PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] User-controllable command-line arguments inappropriately trigger a WARN_ON().
> --
>
> --- Patch [16]: [PATCH v5 16/18] tracing/remotes: Add trace_remote cmdline options ---
> commit 473129b2ec6ced6d4d23093ce86b83497f7202d2
> Author: Vincent Donnefort <vdonnefort@google.com>
>
> tracing/remotes: Add trace_remote cmdline options
>
> This commit adds a trace_remote= boot command-line option to configure a
> trace remote upon registration. It enables configuring various options like
> buffer size, polling interval, and activating specific tracing events.
>
> > diff --git a/kernel/trace/trace_remote.c b/kernel/trace/trace_remote.c
> > index b1c75666ab638..8764d0ed39097 100644
> > --- a/kernel/trace/trace_remote.c
> > +++ b/kernel/trace/trace_remote.c
>
> [ ... ]
>
> > @@ -1169,6 +1171,124 @@ static int poll_ms_show(struct seq_file *s, void *unused)
>
> [ ... ]
>
> > +static void trace_remote_apply_cmdline_opts(struct trace_remote *remote, char *cmdline)
> > +{
>
> [ ... ]
>
> > + } else if (!strncmp(opt, "buf_size=", 9)) {
> > + /* buf_size can only be applied if the buffer is unloaded */
> > + if (!WARN_ON(trace_remote_loaded(remote)))
> > + remote->trace_buffer_size = memparse(opt + 9, NULL);
>
> [Severity: Medium]
> Should this be a pr_warn() instead of a WARN_ON()?
>
> If the bootloader passes multiple trace_remote= parameters, and an earlier
> parameter enables events (which loads the buffer) before a later parameter
> tries to set buf_size= for the same remote, this check will fail and emit a
> warning.
>
> Because WARN_ON() is used here, a simple typo or misordered boot command line
> will trigger a splat and cause a kernel panic during boot on any system
> configured with panic_on_warn.
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260812161340.2417322-1-vdonnefort@google.com?part=16
pr_warn() sounds good
--
Vincent
next prev parent reply other threads:[~2026-08-13 14:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 16:13 [PATCH v5 00/18] tracing/remotes: Add printk, dump_on_panic and boot parameters Vincent Donnefort
2026-08-12 16:13 ` [PATCH v5 01/18] tracing/remotes: Gate tracefs files opening on trace remote registration Vincent Donnefort
2026-08-12 16:31 ` sashiko-bot
2026-08-13 13:16 ` Vincent Donnefort
2026-08-12 16:13 ` [PATCH v5 02/18] tracing/remotes: Release tracefs,eventfs on registration failure Vincent Donnefort
2026-08-12 16:25 ` sashiko-bot
2026-08-13 13:25 ` Vincent Donnefort
2026-08-12 16:13 ` [PATCH v5 03/18] tracing/remotes: Use kstrtobool for boolean tracefs files Vincent Donnefort
2026-08-12 16:13 ` [PATCH v5 04/18] tracing/remotes: Use a single per-remote polling work Vincent Donnefort
2026-08-12 16:13 ` [PATCH v5 05/18] tracing/simple_ring_buffer: Add support for compressed length Vincent Donnefort
2026-08-12 16:42 ` sashiko-bot
2026-08-13 14:00 ` Vincent Donnefort
2026-08-12 16:13 ` [PATCH v5 06/18] tracing/remotes: Add dmesg tracefs file Vincent Donnefort
2026-08-12 16:42 ` sashiko-bot
2026-08-13 14:02 ` Vincent Donnefort
2026-08-12 16:13 ` [PATCH v5 07/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-08-12 16:40 ` sashiko-bot
2026-08-13 14:06 ` Vincent Donnefort
2026-08-12 16:13 ` [PATCH v5 08/18] tracing/remotes: selftests: Prefix hypervisor folder Vincent Donnefort
2026-08-12 16:52 ` sashiko-bot
2026-08-12 16:13 ` [PATCH v5 09/18] ring-buffer: Use irqsave for the reader lock in ring_buffer_poll_remote Vincent Donnefort
2026-08-12 16:13 ` [PATCH v5 10/18] ring-buffer: Use panic-friendly locking in ring_buffer_iter interface Vincent Donnefort
2026-08-12 16:54 ` sashiko-bot
[not found] ` <20260812161340.2417322-15-vdonnefort@google.com>
2026-08-12 17:02 ` [PATCH v5 14/18] tracing/remotes: selftests: Add a test for the dump_on_panic tracefs file sashiko-bot
[not found] ` <20260812161340.2417322-14-vdonnefort@google.com>
2026-08-12 17:08 ` [PATCH v5 13/18] tracing/remotes: Add " sashiko-bot
[not found] ` <20260812161340.2417322-17-vdonnefort@google.com>
2026-08-12 17:11 ` [PATCH v5 16/18] tracing/remotes: Add trace_remote cmdline options sashiko-bot
2026-08-13 14:21 ` Vincent Donnefort [this message]
[not found] ` <20260812161340.2417322-16-vdonnefort@google.com>
2026-08-12 17:13 ` [PATCH v5 15/18] tracing/remotes: Add poll_ms tracefs file sashiko-bot
2026-08-13 14:20 ` Vincent Donnefort
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=an3S5rK5dLZkADSU@google.com \
--to=vdonnefort@google.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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