mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v1] perf trace: Fix possible insufficient allocation of argument formats
Date: Wed, 26 Mar 2025 12:44:51 -0700	[thread overview]
Message-ID: <Z-RZM7X_XCSCxpJV@google.com> (raw)
In-Reply-To: <CAH0uvoi-uxLNOoZ8P1g--jBZUnax_1vCu42SjFCNS7mdAH6Ozg@mail.gmail.com>

On Wed, Mar 26, 2025 at 11:30:11AM -0700, Howard Chu wrote:
> Hello Namhyung,
> 
> LGTM. This is better. :)

Great, can you please resend it with my Suggested-by?

Thanks,
Namhyung

> 
> On Wed, Mar 26, 2025 at 11:21 AM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > 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.
> >
> > Thanks for the fix.  I've noticed this too but I feel like we can make
> > syscall__alloc_arg_fmts() a bit simpler.
> >
> > How about this?
> >
> > Thanks,
> > Namhyung
> >
> >
> > ---8<---
> > diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> > index 6ac51925ea4249c2..b9bdab52f5801c3a 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.49.0.395.g12beb8f557-goog
> >

  reply	other threads:[~2025-03-26 19:44 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
2025-03-26 18:21 ` Namhyung Kim
2025-03-26 18:30   ` Howard Chu
2025-03-26 19:44     ` Namhyung Kim [this message]
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-RZM7X_XCSCxpJV@google.com \
    --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 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®