From: sashiko-bot@kernel.org
To: "Alireza Haghdoost" <haghdoost@uber.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 2/4] perf script: Add --max-symbol-bytes to bound ELF symbol memory
Date: Sun, 20 Sep 2026 02:43:35 +0000 [thread overview]
Message-ID: <20260920024336.67F2A1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260919-perf-symbol-memory-send-v2-2-495b8f00ad7c@uber.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] perf: missing <stdbool.h> in symbol-bytes.c
--
commit 43444932791d9e1c6b50bba8362920738abe2410
Author: Alireza Haghdoost <haghdoost@uber.com>
perf script: Add --max-symbol-bytes to bound ELF symbol memory
This commit adds a new --max-symbol-bytes option to bound the memory consumed
by struct symbol allocations. Once the specified budget is reached, the ELF
loader stops loading new symbols and prints unresolved addresses as unknown.
> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> --- a/tools/perf/builtin-script.c
> +++ b/tools/perf/builtin-script.c
[ ... ]
> @@ -4035,6 +4036,44 @@ static int parse_callret_trace(const struct option *opt __maybe_unused,
> return 0;
> }
>
> +static int parse_max_symbol_bytes(const struct option *opt,
> + const char *str, int unset)
> +{
[ ... ]
> + if (!strcmp(str, "0")) {
> + *max_bytes = 0;
> + return 0;
> + }
> +
> + len = strlen(str);
> + if (len < 2 || !strchr("BKMG", str[len - 1]) ||
> + strspn(str, "0123456789") != len - 1)
[Severity: Low]
This is a pre-existing issue, but parse_max_symbol_bytes() introduces direct
calls to libc string functions like strcmp() and strlen(). Since this file
lacks an explicit include of the POSIX <string.h> header, does this cause
compilation failures in musl libc environments where headers are not
implicitly included?
> diff --git a/tools/perf/tests/symbol-bytes.c b/tools/perf/tests/symbol-bytes.c
> --- /dev/null
> +++ b/tools/perf/tests/symbol-bytes.c
[ ... ]
> +struct reserve_arg {
> + size_t bytes;
> + bool success;
[Severity: Low]
This struct uses the bool type, but the file doesn't explicitly include
<stdbool.h>. Can this cause a compilation failure under stricter libc
environments like musl due to the missing type definition?
> +};
> +
> +static void *reserve_bytes(void *data)
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260919-perf-symbol-memory-send-v2-0-495b8f00ad7c@uber.com?part=2
next prev parent reply other threads:[~2026-09-20 2:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 2:33 [PATCH v2 0/4] perf script: Bounded and lazy symbol loading Alireza Haghdoost via B4 Relay
2026-09-20 2:33 ` [PATCH v2 1/4] perf symbols: Fix broken ELF_C_READ_MMAP fallback guard Alireza Haghdoost via B4 Relay
2026-09-20 2:42 ` sashiko-bot
2026-09-20 23:52 ` Namhyung Kim
2026-09-20 2:33 ` [PATCH v2 2/4] perf script: Add --max-symbol-bytes to bound ELF symbol memory Alireza Haghdoost via B4 Relay
2026-09-20 2:43 ` sashiko-bot [this message]
2026-09-21 0:03 ` Namhyung Kim
2026-09-21 4:27 ` Alireza Haghdoost
2026-09-20 2:33 ` [PATCH v2 3/4] perf script: Add --lazy-load-symbols for lazy symbol loading Alireza Haghdoost via B4 Relay
2026-09-20 2:45 ` sashiko-bot
2026-09-20 13:49 ` Alireza Haghdoost
2026-09-21 0:19 ` Namhyung Kim
2026-09-21 4:45 ` Alireza Haghdoost
2026-09-20 2:33 ` [PATCH v2 4/4] perf test: Test lazy symbol loading and symbol memory limits Alireza Haghdoost via B4 Relay
2026-09-20 2:39 ` sashiko-bot
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=20260920024336.67F2A1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=haghdoost@uber.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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