From: Namhyung Kim <namhyung@kernel.org>
To: Howard Chu <howardchu95@gmail.com>
Cc: acme@kernel.org, mingo@redhat.com, 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 v4] perf trace: Fix possible insufficient allocation of argument formats
Date: Sat, 29 Mar 2025 22:31:01 -0700 [thread overview]
Message-ID: <Z-jXFffv8MMuo2p3@z2> (raw)
In-Reply-To: <20250327150712.1966188-1-howardchu95@gmail.com>
Hello,
On Thu, Mar 27, 2025 at 08:07:12AM -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/),
We usually handle this by adding a footnote style link like, [1].
> 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>
> Suggested-by: Namhyung Kim <namhyung@kernel.org>
> Fixes: c7b87ce0dd10 ("perf trace: Fix runtime error of index out of bounds")
And add the link here.
[1] (actual URL here)
Also you need to keep three dashes "---" before the change log so that
it can be treated as comments (and not added to the commit message).
Please take a look at my previous posting.
https://lore.kernel.org/r/20250326044001.3503432-1-namhyung@kernel.org
Thanks,
Namhyung
>
> Changes in v4:
> - Make the patch apply
>
> Changes in v3:
> - Add 'Fixes:' tag
>
> Changes in v2:
> - Simplify the code (written by Namhyung)
>
> tools/perf/builtin-trace.c | 16 +++++-----------
> 1 file changed, 5 insertions(+), 11 deletions(-)
>
> diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> index a102748bd0c9..439e152186da 100644
> --- a/tools/perf/builtin-trace.c
> +++ b/tools/perf/builtin-trace.c
> @@ -2022,9 +2022,6 @@ static int syscall__alloc_arg_fmts(struct syscall *sc, int nr_args)
> {
> int idx;
>
> - if (nr_args == RAW_SYSCALL_ARGS_NUM && sc->fmt && sc->fmt->nr_args != 0)
> - nr_args = sc->fmt->nr_args;
> -
> sc->arg_fmt = calloc(nr_args, sizeof(*sc->arg_fmt));
> if (sc->arg_fmt == NULL)
> return -1;
> @@ -2034,7 +2031,6 @@ static int syscall__alloc_arg_fmts(struct syscall *sc, int nr_args)
> sc->arg_fmt[idx] = sc->fmt->arg[idx];
> }
>
> - sc->nr_args = nr_args;
> return 0;
> }
>
> @@ -2176,14 +2172,9 @@ static int syscall__read_info(struct syscall *sc, struct trace *trace)
> return err;
> }
>
> - /*
> - * 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))
> - return -ENOMEM;
> -
> sc->args = sc->tp_format->format.fields;
> + sc->nr_args = sc->tp_format->format.nr_fields;
> +
> /*
> * We need to check and discard the first variable '__syscall_nr'
> * or 'nr' that mean the syscall number. It is needless here.
> @@ -2194,6 +2185,9 @@ static int syscall__read_info(struct syscall *sc, struct trace *trace)
> --sc->nr_args;
> }
>
> + if (syscall__alloc_arg_fmts(sc, sc->nr_args))
> + return -ENOMEM;
> +
> sc->is_exit = !strcmp(name, "exit_group") || !strcmp(name, "exit");
> sc->is_open = !strcmp(name, "open") || !strcmp(name, "openat");
>
> --
> 2.45.2
>
next prev parent reply other threads:[~2025-03-30 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 15:07 [PATCH v4] perf trace: Fix possible insufficient allocation of argument formats Howard Chu
2025-03-30 5:31 ` Namhyung Kim [this message]
2025-03-31 16:31 ` 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-jXFffv8MMuo2p3@z2 \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=howardchu95@gmail.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=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 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.