All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Vincent Donnefort" <vdonnefort@google.com>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v6 16/18] tracing/remotes: Add trace_remote cmdline options
Date: Mon, 17 Aug 2026 14:12:51 +0000	[thread overview]
Message-ID: <20260817141252.4FD471F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260817135517.3919534-17-vdonnefort@google.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `dump_on_panic` command-line option sets `remote->panic_on = true` but fails to dynamically register the panic handler if the trace buffer is already loaded.
--

--- Patch [16]: [PATCH v6 16/18] tracing/remotes: Add trace_remote cmdline options ---
commit 16551de261e3bdeffe51c1a5227c6a115ddbe725
Author: Vincent Donnefort <vdonnefort@google.com>

tracing/remotes: Add trace_remote cmdline options
    
This commit introduces command-line options for trace remotes, allowing
configuration of features like dump_on_panic, dmesg, buf_size, and poll,
as well as enabling specific trace events automatically on boot.

> diff --git a/kernel/trace/trace_remote.c b/kernel/trace/trace_remote.c
> index 204d5bef7a8c4..34847463d9e43 100644
> --- a/kernel/trace/trace_remote.c
> +++ b/kernel/trace/trace_remote.c

[ ... ]

> @@ -1170,6 +1172,126 @@ static int poll_ms_show(struct seq_file *s, void *unused)
> +static void trace_remote_apply_cmdline_opts(struct trace_remote *remote, char *cmdline)
> +{
> +	bool dmesg_on = false;
> +	char *opt;
> +	int ret;
> +
> +	while ((opt = strsep(&cmdline, "^"))) {
> +		if (!*opt)
> +			continue;
> +
> +		if (!strcmp(opt, "dump_on_panic")) {
> +			remote->panic_on = true;

[Severity: Medium]
If the trace remote was configured across multiple command line arguments, and
an earlier argument already enabled events (which loads the trace buffer via
trace_remote_enable_tracing()), will setting remote->panic_on = true here
fail to register the panic notifier?

Since this doesn't call trace_remote_panic_load() if the buffer is already
loaded, it appears the panic handler might never be registered under this
configuration pattern.

> +		} else if (!strcmp(opt, "dmesg")) {
> +			dmesg_on = true;
> +		} else if (!strncmp(opt, "buf_size=", 9)) {
> +			/* buf_size can only be applied if the buffer is unloaded */
> +			if (trace_remote_loaded(remote))
> +				pr_warn("Cannot apply buf_size after events are enabled\n");
> +			else
> +				remote->trace_buffer_size = memparse(opt + 9, NULL);

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260817135517.3919534-1-vdonnefort@google.com?part=16

  reply	other threads:[~2026-08-17 14:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 13:54 [PATCH v6 00/18] tracing/remotes: Add printk, dump_on_panic and boot parameters Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 01/18] tracing/remotes: Gate tracefs files opening on trace remote registration Vincent Donnefort
2026-08-17 14:09   ` sashiko-bot
2026-08-17 13:55 ` [PATCH v6 02/18] tracing/remotes: Release tracefs,eventfs on registration failure Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 03/18] tracing/remotes: Use kstrtobool for boolean tracefs files Vincent Donnefort
2026-08-17 14:11   ` sashiko-bot
2026-08-17 13:55 ` [PATCH v6 04/18] tracing/remotes: Use a single per-remote polling work Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 05/18] tracing/simple_ring_buffer: Add support for compressed length Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 06/18] tracing/remotes: Add dmesg tracefs file Vincent Donnefort
2026-08-17 14:09   ` sashiko-bot
2026-08-17 13:55 ` [PATCH v6 07/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-08-17 14:05   ` sashiko-bot
2026-08-17 13:55 ` [PATCH v6 08/18] tracing/remotes: selftests: Prefix hypervisor folder Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 09/18] ring-buffer: Use irqsave for the reader lock in ring_buffer_poll_remote Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 10/18] ring-buffer: Use panic-friendly locking in ring_buffer_iter interface Vincent Donnefort
2026-08-17 14:04   ` sashiko-bot
2026-08-17 13:55 ` [PATCH v6 11/18] ring-buffer: Add ring_buffer_read_remote_meta_page() Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 12/18] ring-buffer: Add kerneldoc for ring_buffer_poll_remote Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 13/18] tracing/remotes: Add dump_on_panic tracefs file Vincent Donnefort
2026-08-17 14:10   ` sashiko-bot
2026-08-17 13:55 ` [PATCH v6 14/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-08-17 14:07   ` sashiko-bot
2026-08-17 13:55 ` [PATCH v6 15/18] tracing/remotes: Add poll_ms " Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 16/18] tracing/remotes: Add trace_remote cmdline options Vincent Donnefort
2026-08-17 14:12   ` sashiko-bot [this message]
2026-08-17 13:55 ` [PATCH v6 17/18] Documentation: tracing/remotes: Add detailed tracefs layout Vincent Donnefort
2026-08-17 13:55 ` [PATCH v6 18/18] Documentation/kernel-parameters: Add trace_remote Vincent Donnefort
2026-08-17 14:21   ` sashiko-bot

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=20260817141252.4FD471F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vdonnefort@google.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 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.