From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2] perf test: Fix inet_pton probe failure and unroll call graph
Date: Sat, 11 Apr 2026 19:54:22 +0000 [thread overview]
Message-ID: <20260411195423.4C949C2BCAF@smtp.kernel.org> (raw)
In-Reply-To: <20260411193705.735269-1-irogers@google.com>
Sashiko AI review found 1 potential issue(s):
- [Medium] Unconditionally requiring DWARF call-graphs causes the test to falsely fail on perf builds lacking DWARF support.
--
commit dbec7073d294917f7866e8ea3a6b39004a7407ad
Author: Ian Rogers <irogers@google.com>
perf test: Fix inet_pton probe failure and unroll call graph
This commit fixes an issue where multiple identical event names were output
by perf probe when creating multiple probe points, which broke subsequent
commands. It also updates the backtrace collection to explicitly request
dwarf call-graphs and increases max-stack to 8 for all architectures.
> diff --git a/tools/perf/tests/shell/record+probe_libc_inet_pton.sh b/tools/perf/tests/shell/record+probe_libc_inet_pton.sh
> index ab99bef556bf0..eca629ee83f03 100755
> --- a/tools/perf/tests/shell/record+probe_libc_inet_pton.sh
> +++ b/tools/perf/tests/shell/record+probe_libc_inet_pton.sh
[ ... ]
> @@ -40,12 +40,12 @@ trace_libc_inet_pton_backtrace() {
> echo ".*inet_pton\+0x[[:xdigit:]]+[[:space:]]\($libc|inlined\)$" >> $expected
> case "$(uname -m)" in
> s390x)
> - eventattr='call-graph=dwarf,max-stack=4'
> + eventattr='call-graph=dwarf,max-stack=8'
> echo "((__GI_)?getaddrinfo|text_to_binary_address)\+0x[[:xdigit:]]+[[:space:]]\($libc|inlined\)$" >> $expected
> echo "(gaih_inet|main)\+0x[[:xdigit:]]+[[:space:]]\(inlined|.*/bin/ping.*\)$" >> $expected
> ;;
> *)
> - eventattr='max-stack=4'
> + eventattr='call-graph=dwarf,max-stack=8'
Will this cause the test to falsely fail on perf builds lacking DWARF support?
If perf is compiled without libunwind or libdw, running perf record with
call-graph=dwarf will exit with an error. Since the test script doesn't
appear to verify DWARF support before running, the test will report a hard
failure rather than gracefully skipping on minimal perf builds.
> echo ".*(\+0x[[:xdigit:]]+|\[unknown\])[[:space:]]\(.*/bin/ping.*\)$" >> $expected
> ;;
> esac
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260411193705.735269-1-irogers@google.com?part=1
next prev parent reply other threads:[~2026-04-11 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 0:23 [PATCH v1] perf test: Fix inet_pton probe failure due to multiple probes Ian Rogers
2026-04-10 0:38 ` sashiko-bot
2026-04-11 19:37 ` [PATCH v2] perf test: Fix inet_pton probe failure and unroll call graph Ian Rogers
2026-04-11 19:54 ` sashiko-bot [this message]
2026-04-12 1:14 ` Ian Rogers
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=20260411195423.4C949C2BCAF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko@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