From: sashiko-bot@kernel.org
To: "Jim Cromie" <jim.cromie@gmail.com>,
"Jason Baron" <jbaron@akamai.com>,
"Shuah Khan" <shuah@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Arnd Bergmann" <arnd@arndb.de>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Petr Pavlu" <petr.pavlu@suse.com>,
"Daniel Gomez" <da.gomez@kernel.org>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Aaron Tomlin" <atomlin@atomlin.com>,
"Jonathan Corbet" <corbet@net.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Pavel Machek" <pavel@kernel.org>, "Len Brown" <lenb@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Petr Mladek" <pmladek@suse.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"John Ogness" <john.ogness@linutronix.de>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: dri-devel@lists.freedesktop.org, linux-modules@vger.kernel.org,
linux-kbuild@vger.kernel.org, "Jason Baron" <jbaron@redhat.com>
Subject: Re: [PATCH v13 30/39] dyndbg: split multi-query strings with @
Date: Wed, 28 Oct 2026 20:25:20 +0000 [thread overview]
Message-ID: <sashiko-outbox-188406@kernel.org> (raw)
In-Reply-To: <20261027-dd-cmap-part2-clean-v13-30-9267923be612@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dyndbg: ddebug_find_delimiter() tracks quotes across comments and newlines
--
commit 0c538c4aea6cd34ef1fce80f637f8815b5c63761
Author: Jim Cromie <jim.cromie@gmail.com>
dyndbg: split multi-query strings with @
This commit adds '@' as a multi-command delimiter alongside ';' and '\n' in
dynamic debug queries, using a quote-aware helper ddebug_find_delimiter() to
avoid splitting on delimiters inside quoted strings. It also updates the
dynamic debug documentation and selftests accordingly.
> diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
> index 5d99c3aef5a16..11f7350f35907 100644
> --- a/lib/dynamic_debug.c
> +++ b/lib/dynamic_debug.c
> @@ -622,6 +622,30 @@ static int ddebug_exec_query(char *query_string, const char *modname)
> return nfound;
> }
>
> +/*
> + * Split multi-query string on delimiters (@, ;, \n), ignoring delimiters
> + * that appear inside single or double quoted strings.
> + */
> +static char *ddebug_find_delimiter(char *str, const char *delims)
> +{
> + bool in_quote = false;
> + char quote_char = 0;
> +
> + for (; *str; str++) {
> + if (*str == '"' || *str == '\'') {
> + if (!in_quote) {
> + in_quote = true;
> + quote_char = *str;
> + } else if (*str == quote_char) {
> + in_quote = false;
> + }
> + } else if (!in_quote && strchr(delims, *str)) {
> + return str;
> + }
> + }
> + return NULL;
> +}
> +
> /* handle multiple queries in query string, continue on error, return
> last error or number of matching callsites. Module name is either
> in the modname arg (for boot args) or perhaps in query string.
> @@ -632,7 +656,7 @@ static int ddebug_exec_queries(char *query, const char *modname)
> int i, errs = 0, exitcode = 0, rc, nfound = 0;
>
> for (i = 0; query; query = split) {
> - split = strpbrk(query, ";\n");
> + split = ddebug_find_delimiter(query, "@;\n");
> if (split)
> *split++ = '\0';
[Severity: Medium]
Can ddebug_find_delimiter() drop or merge subsequent lines in a multi-line
query when a '#' comment contains an apostrophe or when a line has an
unclosed quote?
Previously, ddebug_exec_queries() called strpbrk(query, ";\n"), which
unconditionally split the input buffer on '\n' before comment handling in
ddebug_exec_queries() and ddebug_tokenize():
lib/dynamic_debug.c:ddebug_exec_queries() {
...
query = skip_spaces_and_commas(query);
if (!query || !*query || *query == '#')
continue;
...
}
lib/dynamic_debug.c:ddebug_tokenize() {
...
while (*buf) {
...
if (*buf == '#')
break; /* token starts comment, skip rest of line */
...
}
With ddebug_find_delimiter(query, "@;\n"), quote state is tracked across '#'
comments and across '\n'. If a multi-line write to
/proc/dynamic_debug/control contains an apostrophe inside a comment, such as:
# don't enable foo
func bar +p
or an inline comment:
func foo +p # module's debug
func bar +p
ddebug_find_delimiter() sets in_quote = true on the '\'' and ignores the '\n'
at the end of the comment line. As a result, "func bar +p" is merged into the
commented line and silently discarded when ddebug_exec_queries() or
ddebug_tokenize() skips the comment.
Similarly, if a line has an unclosed quote, ddebug_find_delimiter() no longer
splits at '\n'. On a multi-line buffer, subsequent lines are concatenated
into the broken line instead of failing that line and continuing. On a
single-line write via echo, the trailing '\n' is left attached to the query
string and emitted in the v2pr_info() and pr_err("unclosed quote: %s\n", buf)
messages, which also appears to be why the golden hashes for the unclosed
quote tests (FT_grammar_errs.1, FT_grammar_errs.21, and FT_grammar_errs.41)
changed in GOLDEN_RECORDS in
tools/testing/selftests/dynamic_debug/dyndbg_selftest.sh.
Should '\n' always terminate a query (and reset quote state, or be split
before scanning for ';' and '@'), and should '#' comments outside quotes skip
to the end of the line?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261027-dd-cmap-part2-clean-v13-0-9267923be612@gmail.com?part=30
next prev parent reply other threads:[~2026-10-28 20:25 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 20:22 [PATCH v13 00/39] dyndbg: Fix classmaps API for subsystems, query extensions, selftests Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 01/39] selftests/dyndbg: Add kselftest script to verify dynamic-debug Jim Cromie via B4 Relay
2026-10-28 20:25 ` sashiko-bot
2026-10-27 20:22 ` [PATCH v13 02/39] vmlinux.lds.h: refactor BOUNDED_SECTION_* macros into bounded_sections.lds.h Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 03/39] vmlinux.lds.h: drop unused HEADERED_SECTION* macros Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 04/39] vmlinux.lds.h: Fix ALIGN(8) omission causing NULL ptr on i386 Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 05/39] vmlinux.lds.h: remove redundant ALIGN(8) directives Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 06/39] dyndbg.lds.S: fix lost dyndbg sections in modules Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 07/39] dyndbg: factor ddebug_match_desc out from ddebug_change Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 08/39] dyndbg: add stub macro for DECLARE_DYNDBG_CLASSMAP Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 09/39] dyndbg: reword "class unknown," to "class:_UNKNOWN_" Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 10/39] dyndbg-API: remove DD_CLASS_TYPE_(DISJOINT|LEVEL)_NAMES and code Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 11/39] dyndbg: drop NUM_TYPE_ARGS Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 12/39] dyndbg: bump num-tokens in a query-cmd from 9 to 15 Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 13/39] dyndbg: reduce verbose/debug clutter Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 14/39] dyndbg: refactor param_set_dyndbg_classes and below Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 15/39] dyndbg: tighten fn-sig of ddebug_apply_class_bitmap Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 16/39] dyndbg: replace classmap list with an array-slice Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 17/39] dyndbg: macrofy a 2-index for-loop pattern Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 18/39] dyndbg: reduce class param storage to u32 Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 19/39] dyndbg,module: make proper substructs in _ddebug_info Jim Cromie via B4 Relay
2026-10-28 20:25 ` sashiko-bot
2026-10-27 20:22 ` [PATCH v13 20/39] dyndbg: move mod_name down from struct ddebug_table to _ddebug_info Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 21/39] dyndbg: hoist classmap-filter-by-modname up to ddebug_add_module Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 22/39] dyndbg-API: replace DECLARE_DYNDBG_CLASSMAP Jim Cromie via B4 Relay
2026-10-28 20:25 ` sashiko-bot
2026-10-27 20:22 ` [PATCH v13 23/39] selftests/dyndbg: add FT_classmap_inheritance Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 24/39] dyndbg: detect class_id reservation conflicts Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 25/39] dyndbg: check DYNAMIC_DEBUG_CLASSMAP_{DEFINE,USE_} args at compile-time Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 26/39] dyndbg-test: add do_bulk testpoint, rename do_prints to do_classes Jim Cromie via B4 Relay
2026-10-28 20:25 ` sashiko-bot
2026-10-27 20:22 ` [PATCH v13 27/39] dyndbg-API: promote DYNAMIC_DEBUG_CLASSMAP_PARAM to API Jim Cromie via B4 Relay
2026-10-28 20:25 ` sashiko-bot
2026-10-27 20:22 ` [PATCH v13 28/39] dyndbg: control-parser: treat comma as a token separator Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 29/39] selftests: enable comma-terminator tests Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 30/39] dyndbg: split multi-query strings with @ Jim Cromie via B4 Relay
2026-10-28 20:25 ` sashiko-bot [this message]
2026-10-27 20:22 ` [PATCH v13 31/39] dyndbg: resolve "protection" of class'd pr_debug Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 32/39] docs/dyndbg: add classmap info to howto Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 33/39] dyndbg: add epilogue to dynamic_debug/control file Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 34/39] dyndbg: fix attempt to modify an RO string Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 35/39] dyndbg: add +c flag to count pr_debug calls without printing Jim Cromie via B4 Relay
2026-10-28 20:25 ` sashiko-bot
2026-10-27 20:22 ` [PATCH v13 36/39] dyndbg: add DEBUG-biased fallback stubs for _dynamic_func_call_cls Jim Cromie via B4 Relay
2026-10-28 20:25 ` sashiko-bot
2026-10-27 20:22 ` [PATCH v13 37/39] selftests/dyndbg: Add FT_count_calls to test +c flag Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 38/39] printk.h: fix overzealous pr_fmt in pr_debug_ratelimited Jim Cromie via B4 Relay
2026-10-27 20:22 ` [PATCH v13 39/39] drm: Mark __drm_debug as __read_mostly Jim Cromie via B4 Relay
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=sashiko-outbox-188406@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Jason@zx2c4.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=atomlin@atomlin.com \
--cc=corbet@lwn.net \
--cc=corbet@net.net \
--cc=da.gomez@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=jbaron@redhat.com \
--cc=jim.cromie@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=lenb@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcgrof@kernel.org \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=pavel@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=senozhatsky@chromium.org \
--cc=shuah@kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=tzimmermann@suse.de \
/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