From: sashiko-bot@kernel.org
To: "Thomas Richter" <tmricht@linux.ibm.com>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH V2 linux-next] perf test: Skip failing 'perf test aslr' test case
Date: Mon, 29 Jun 2026 11:12:50 +0000 [thread overview]
Message-ID: <20260629111251.0E0441F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260629110559.1283453-1-tmricht@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Commit message contradicts script behavior regarding test skip exit code, hiding skipped status from the test runner.
--
commit 0ec9bd8ca22ab0ece501382558440bfde5e6fdd0
Author: Thomas Richter <tmricht@linux.ibm.com>
perf test: Skip failing 'perf test aslr' test case
This commit addresses a failure in the 'perf test aslr' test case on s390
due to missing dwarf call-graph support in perf inject. It modifies
the script to drop the stack user sample and emit a skip message instead of
failing.
> diff --git a/tools/perf/tests/shell/inject_aslr.sh b/tools/perf/tests/shell/inject_aslr.sh
> index c00461828ea79..d83c2591db8f6 100755
> --- a/tools/perf/tests/shell/inject_aslr.sh
> +++ b/tools/perf/tests/shell/inject_aslr.sh
> @@ -135,8 +135,14 @@ test_callchain_aslr() {
> echo "Callchain ASLR test [Failed - no noploop samples in original file]"
> err=1
> elif [ -z "$new_addr" ]; then
> - echo "Callchain ASLR test [Failed - could not find remapped address]"
> - err=1
> + if perf evlist -v -i "${data}" | grep -q 'sample_type:.*STACK_USER'; then
> + echo "Dropping stack user sample as possible ASLR leak"
> + echo "Call-graph dwarf not supported with 'perf inject --aslr'"
> + echo "Callchain ASLR test [Skip]"
[Severity: Medium]
The commit message states "Since one subtest is skipped, the complete test is
reported as skipped." However, it appears err is not set to 2 (the standard skip
code) here, meaning the script will exit with 0 (Ok) rather than being reported
as skipped by the test runner.
If setting err=2 was intentionally avoided because the script's cleanup
function currently assumes any non-zero exit code is a failure and leaves
temporary directories behind, would it be better to redesign the error
handling to support returning 2 without leaking temp files, or should the
commit message be corrected to reflect the actual exit status?
> + else
> + echo "Callchain ASLR test [Failed - could not find remapped address]"
> + err=1
> + fi
> elif [ "$orig_addr" = "$new_addr" ]; then
> echo "Callchain ASLR test [Failed - addresses are not remapped]"
> err=1
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260629110559.1283453-1-tmricht@linux.ibm.com?part=1
next prev parent reply other threads:[~2026-06-29 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 11:05 [PATCH V2 linux-next] perf test: Skip failing 'perf test aslr' test case Thomas Richter
2026-06-29 11:12 ` sashiko-bot [this message]
2026-06-30 23:35 ` Namhyung Kim
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=20260629111251.0E0441F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tmricht@linux.ibm.com \
/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