From: Steven Rostedt <rostedt@goodmis.org>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
tom.zanussi@linux.intel.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tracing/hist: bound full field-name construction
Date: Sun, 29 Mar 2026 14:39:49 -0400 [thread overview]
Message-ID: <20260329143949.35659b68@gandalf.local.home> (raw)
In-Reply-To: <20260329030950.32503-1-pengpeng@iscas.ac.cn>
On Sun, 29 Mar 2026 11:09:49 +0800
Pengpeng Hou <pengpeng@iscas.ac.cn> wrote:
> hist_field_name() builds a fully qualified synthetic field name in a
> fixed MAX_FILTER_STR_VAL buffer using repeated strcat() calls. Long
> system, event, and field names can therefore overflow the static staging
> buffer.
>
> Build the qualified name with snprintf() and fall back to the plain
> field name if it does not fit.
The fallback breaks
>
> Fixes: 067fe038e70f ("tracing: Add variable reference handling to hist triggers")
Do you have any examples where it actually does overflow or is this just theoretical?
If it's just theoretical, it does not get a "Fixes" tag.
Hmm, but actually I don't see it resetting full_name to a '\0' so I can see
this concatenating on top of a previous value. THAT would need fixing and
require a fixes tag. An example of triggering the overflow would also be
required.
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
> ---
> kernel/trace/trace_events_hist.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
> index 73ea180cad55..4a27da628a71 100644
> --- a/kernel/trace/trace_events_hist.c
> +++ b/kernel/trace/trace_events_hist.c
> @@ -1362,12 +1362,12 @@ static const char *hist_field_name(struct hist_field *field,
> if (field->system) {
> static char full_name[MAX_FILTER_STR_VAL];
>
> - strcat(full_name, field->system);
> - strcat(full_name, ".");
> - strcat(full_name, field->event_name);
> - strcat(full_name, ".");
> - strcat(full_name, field->name);
> - field_name = full_name;
> + if (snprintf(full_name, sizeof(full_name), "%s.%s.%s",
> + field->system, field->event_name,
> + field->name) < sizeof(full_name))
Ug, please do not use a horribly looking if conditional. And it should most
definitely error on overflow: Break it up:
if (field->system) {
static char full_name[MAX_FILTER_STR_VAL];
int len;
len = snprintf(full_name, sizeof(full_name), "%s.%s.%s",
field->system, field->event_name,
field->name);
if (len >= size(full_name))
return NULL;
field_name = full_name;
> + field_name = full_name;
> + else
> + field_name = field->name;
> } else
> field_name = field->name;
> } else if (field->flags & HIST_FIELD_FL_TIMESTAMP)
-- Steve
next prev parent reply other threads:[~2026-03-29 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 3:09 [PATCH 1/2] tracing/hist: bound full field-name construction Pengpeng Hou
2026-03-29 18:39 ` Steven Rostedt [this message]
2026-03-30 2:46 ` [PATCH v2 1/2] tracing/hist: rebuild full_name on each hist_field_name() call Pengpeng Hou
2026-03-30 14:22 ` Steven Rostedt
2026-04-01 11:22 ` Pengpeng Hou
2026-04-08 1:05 ` Steven Rostedt
2026-04-08 15:58 ` Tom Zanussi
2026-04-08 16:25 ` Steven Rostedt
2026-04-08 17:18 ` Tom Zanussi
2026-04-08 2:15 ` Pengpeng Hou
2026-04-08 2:14 ` Steven Rostedt
2026-04-13 22:38 ` Tom Zanussi
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=20260329143949.35659b68@gandalf.local.home \
--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 \
--cc=tom.zanussi@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox