From: Steven Rostedt <rostedt@goodmis.org>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing/hist: bound expression strings with seq_buf
Date: Tue, 14 Apr 2026 05:10:10 -0400 [thread overview]
Message-ID: <20260414051010.200075d8@robin> (raw)
In-Reply-To: <20260409123001.1-tracing-hist-expr-v2-pengpeng@iscas.ac.cn>
On Thu, 9 Apr 2026 10:56:28 +0800
Pengpeng Hou <pengpeng@iscas.ac.cn> wrote:
Hi Pengpeng,
Again, subject should be:
tracing: Bound histogram expression strings with seq_buf
> expr_str() allocates a fixed MAX_FILTER_STR_VAL buffer and then builds
> expression names with a series of raw strcat() appends. Nested operands,
> constants and field flags can push the rendered string past that fixed
> limit before the name is attached to the hist field.
>
> Build the expression strings with seq_buf and propagate failures back to
> the expression parser when the rendered name would exceed
> MAX_FILTER_STR_VAL.
>
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
> ---
> Changes since v1:
> - replace the previous bounded append helper and manual length tracking
> with seq_buf as suggested by Steven Rostedt
> - keep the -E2BIG propagation back into parse_unary() and parse_expr()
>
> kernel/trace/trace_events_hist.c | 93 ++++++++++++++++++++++----------
> 1 file changed, 64 insertions(+), 29 deletions(-)
>
> diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
> index 73ea180cad55..09aaedb92993 100644
> --- a/kernel/trace/trace_events_hist.c
> +++ b/kernel/trace/trace_events_hist.c
> @@ -8,6 +8,7 @@
> #include <linux/module.h>
> #include <linux/kallsyms.h>
> #include <linux/security.h>
> +#include <linux/seq_buf.h>
> #include <linux/mutex.h>
> #include <linux/slab.h>
> #include <linux/stacktrace.h>
> @@ -1738,85 +1739,104 @@ static const char *get_hist_field_flags(struct hist_field *hist_field)
> return flags_str;
> }
>
> -static void expr_field_str(struct hist_field *field, char *expr)
> +static bool expr_field_str(struct hist_field *field, struct seq_buf *s)
> {
> + const char *field_name;
> +
> if (field->flags & HIST_FIELD_FL_VAR_REF)
> - strcat(expr, "$");
> - else if (field->flags & HIST_FIELD_FL_CONST) {
> - char str[HIST_CONST_DIGITS_MAX];
> + seq_buf_putc(s, '$');
> + else if (field->flags & HIST_FIELD_FL_CONST)
> + seq_buf_printf(s, "%llu", field->constant);
>
> - snprintf(str, HIST_CONST_DIGITS_MAX, "%llu", field->constant);
> - strcat(expr, str);
> - }
> + field_name = hist_field_name(field, 0);
> + if (!field_name)
> + return false;
>
> - strcat(expr, hist_field_name(field, 0));
> + seq_buf_puts(s, field_name);
>
> if (field->flags && !(field->flags & HIST_FIELD_FL_VAR_REF)) {
> const char *flags_str = get_hist_field_flags(field);
>
> - if (flags_str) {
> - strcat(expr, ".");
> - strcat(expr, flags_str);
> - }
> + if (flags_str)
> + seq_buf_printf(s, ".%s", flags_str);
> }
> +
> + return !seq_buf_has_overflowed(s);
> }
>
> static char *expr_str(struct hist_field *field, unsigned int level)
> {
> char *expr;
> + struct seq_buf s;
> + int ret = -E2BIG;
>
> if (level > 1)
> - return NULL;
> + return ERR_PTR(-EINVAL);
>
> expr = kzalloc(MAX_FILTER_STR_VAL, GFP_KERNEL);
> if (!expr)
> - return NULL;
> + return ERR_PTR(-ENOMEM);
A patch should do one thing at a time. This patch appears to be doing
two things: fixing the bound strings, returning errors instead of NULL.
Please split this up into two patches. One that changes the return
values from NULL to ERR_PTR() and the other to use seq_buf.
Thanks,
-- Steve
prev parent reply other threads:[~2026-04-14 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 6:09 [PATCH] tracing/hist: bound expression string construction Pengpeng Hou
2026-04-08 21:27 ` Steven Rostedt
2026-04-09 2:56 ` [PATCH v2] tracing/hist: bound expression strings with seq_buf Pengpeng Hou
2026-04-14 9:10 ` Steven Rostedt [this message]
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=20260414051010.200075d8@robin \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=pengpeng@iscas.ac.cn \
/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