From: Howard Chu <howardchu95@gmail.com>
To: acme@kernel.org
Cc: mingo@redhat.com, namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
peterz@infradead.org, kan.liang@linux.intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf trace: Fix possible insufficient allocation of argument formats
Date: Mon, 24 Mar 2025 16:58:41 -0700 [thread overview]
Message-ID: <Z-HxsV8KyeTWeskb@gmail.com> (raw)
In-Reply-To: <20250324235245.613063-1-howardchu95@gmail.com>
Hello,
Forgot to add, there should be:
Fixes: c7b87ce0dd10 ("perf trace: Fix runtime error of index out of bounds")
Thanks,
Howard
On Mon, Mar 24, 2025 at 04:52:45PM -0700, Howard Chu wrote:
> In my previous fix of runtime error(Link:
> https://lore.kernel.org/linux-perf-users/20250122025519.361873-1-howardchu95@gmail.com/),
> I made a mistake of decrementing one unconditionally, regardless of
> whether an extra 'syscall_nr' or 'nr' field was present in
> libtraceevent's tp_format. This may cause perf trace to allocate one
> fewer arg_fmt entry than needed for the accurate representation of syscall
> arguments.
>
> This patch corrects the mistake by checking the presence of'syscall_nr' or
> 'nr', and adjusting the length of arg_fmt[] accordingly.
>
> Signed-off-by: Howard Chu <howardchu95@gmail.com>
> ---
> tools/perf/builtin-trace.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> index a102748bd0c9..ad6dad8e2453 100644
> --- a/tools/perf/builtin-trace.c
> +++ b/tools/perf/builtin-trace.c
> @@ -2139,6 +2139,7 @@ static int syscall__read_info(struct syscall *sc, struct trace *trace)
> char tp_name[128];
> const char *name;
> int err;
> + bool extra_nr = false;
>
> if (sc->nonexistent)
> return -EEXIST;
> @@ -2176,20 +2177,22 @@ static int syscall__read_info(struct syscall *sc, struct trace *trace)
> return err;
> }
>
> + sc->args = sc->tp_format->format.fields;
> + if (!strcmp(sc->args->name, "__syscall_nr") || !strcmp(sc->args->name, "nr"))
> + extra_nr = true;
> /*
> * The tracepoint format contains __syscall_nr field, so it's one more
> * than the actual number of syscall arguments.
> */
> - if (syscall__alloc_arg_fmts(sc, sc->tp_format->format.nr_fields - 1))
> + if (syscall__alloc_arg_fmts(sc, sc->tp_format->format.nr_fields - (extra_nr ? 1 : 0)))
> return -ENOMEM;
>
> - sc->args = sc->tp_format->format.fields;
> /*
> * We need to check and discard the first variable '__syscall_nr'
> * or 'nr' that mean the syscall number. It is needless here.
> * So drop '__syscall_nr' or 'nr' field but does not exist on older kernels.
> */
> - if (sc->args && (!strcmp(sc->args->name, "__syscall_nr") || !strcmp(sc->args->name, "nr"))) {
> + if (sc->args && extra_nr) {
> sc->args = sc->args->next;
> --sc->nr_args;
> }
> --
> 2.45.2
>
next prev parent reply other threads:[~2025-03-24 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 23:52 Howard Chu
2025-03-24 23:58 ` Howard Chu [this message]
2025-03-26 18:21 ` Namhyung Kim
2025-03-26 18:30 ` Howard Chu
2025-03-26 19:44 ` Namhyung Kim
2025-03-26 19:52 ` Howard Chu
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=Z-HxsV8KyeTWeskb@gmail.com \
--to=howardchu95@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®