From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Dima Kogan <dima@secretsauce.net>,
james.clark@linaro.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] perf: Dynamically allocate buffer for event string
Date: Fri, 11 Oct 2024 00:21:00 +0900 [thread overview]
Message-ID: <20241011002100.e0393340f950e2dc47c76f14@kernel.org> (raw)
In-Reply-To: <20241007141116.882450-2-leo.yan@arm.com>
On Mon, 7 Oct 2024 15:11:14 +0100
Leo Yan <leo.yan@arm.com> wrote:
> Dynamically allocate and free buffer to support event name.
Sorry, but I don't see any benefit from this patch. This looks making
code more complex.
Thank you,
>
> Signed-off-by: Leo Yan <leo.yan@arm.com>
> ---
> tools/perf/util/probe-event.c | 24 ++++++++++++++++++------
> 1 file changed, 18 insertions(+), 6 deletions(-)
>
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index a17c9b8a7a79..cad11d95af4f 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -2834,6 +2834,9 @@ static void warn_uprobe_event_compat(struct probe_trace_event *tev)
> free(buf);
> }
>
> +/* Defined in kernel/trace/trace.h */
> +#define MAX_EVENT_NAME_LEN 64
> +
> /* Set new name from original perf_probe_event and namelist */
> static int probe_trace_event__set_name(struct probe_trace_event *tev,
> struct perf_probe_event *pev,
> @@ -2841,9 +2844,13 @@ static int probe_trace_event__set_name(struct probe_trace_event *tev,
> bool allow_suffix)
> {
> const char *event, *group;
> - char buf[64];
> + char *buf;
> int ret;
>
> + buf = malloc(MAX_EVENT_NAME_LEN);
> + if (!buf)
> + return -ENOMEM;
> +
> /* If probe_event or trace_event already have the name, reuse it */
> if (pev->event && !pev->sdt)
> event = pev->event;
> @@ -2866,17 +2873,19 @@ static int probe_trace_event__set_name(struct probe_trace_event *tev,
> group = PERFPROBE_GROUP;
>
> /* Get an unused new event name */
> - ret = get_new_event_name(buf, sizeof(buf), event, namelist,
> + ret = get_new_event_name(buf, MAX_EVENT_NAME_LEN, event, namelist,
> tev->point.retprobe, allow_suffix);
> if (ret < 0)
> - return ret;
> + goto out;
>
> event = buf;
>
> tev->event = strdup(event);
> tev->group = strdup(group);
> - if (tev->event == NULL || tev->group == NULL)
> - return -ENOMEM;
> + if (tev->event == NULL || tev->group == NULL) {
> + ret = -ENOMEM;
> + goto out;
> + }
>
> /*
> * Add new event name to namelist if multiprobe event is NOT
> @@ -2885,7 +2894,10 @@ static int probe_trace_event__set_name(struct probe_trace_event *tev,
> */
> if (!multiprobe_event_is_supported())
> strlist__add(namelist, event);
> - return 0;
> +
> +out:
> + free(buf);
> + return ret < 0 ? ret : 0;
> }
>
> static int __open_probe_file_and_namelist(bool uprobe,
> --
> 2.34.1
>
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2024-10-10 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 14:11 [PATCH v1 0/3] perf probe: Support long symbol Leo Yan
2024-10-07 14:11 ` [PATCH v1 1/3] perf: Dynamically allocate buffer for event string Leo Yan
2024-10-10 15:21 ` Masami Hiramatsu [this message]
2024-10-07 14:11 ` [PATCH v1 2/3] perf probe: Check group string length Leo Yan
2024-10-10 15:22 ` Masami Hiramatsu
2024-10-07 14:11 ` [PATCH v1 3/3] perf probe: Generate hash event for long symbol Leo Yan
2024-10-10 15:34 ` Masami Hiramatsu
2024-10-10 15:53 ` Leo Yan
2024-10-11 3:07 ` Masami Hiramatsu
2024-10-11 8:41 ` Leo Yan
2024-10-12 5:30 ` Masami Hiramatsu
2024-10-12 14:21 ` Leo Yan
2024-10-10 1:12 ` [PATCH v1 0/3] perf probe: Support " Namhyung Kim
2024-10-10 14:48 ` Masami Hiramatsu
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=20241011002100.e0393340f950e2dc47c76f14@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dima@secretsauce.net \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).