From: sashiko-bot@kernel.org
To: "Song Liu" <song@kernel.org>, live-patching@vger.kernel.org
Cc: peterz@infradead.org, jikos@kernel.org, pmladek@suse.com,
joe.lawrence@redhat.com, puranjay@kernel.org, mbenes@suse.cz,
jpoimboe@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH 10/58] objtool: Keep failing test workdirs by default
Date: Fri, 11 Sep 2026 19:07:04 +0000 [thread overview]
Message-ID: <20260911190705.248B91F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260911184305.1457308-11-song@kernel.org>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] Tests that fail due to unexpected termination (e.g., shell errors, signals) or undeclared skips have their working directories incorrectly deleted despite KEEP=failed, while the runner falsely claims they were kept.
- [Medium] When a test is executed standalone (not via run-tests.sh) and fails, KEEP=failed silently leaks the temporary directory without printing its path.
--
commit 14c7ac654e8638035a6ea9f8c26ee25df0293be4
Author: Joe Lawrence <joe.lawrence@redhat.com>
objtool: Keep failing test workdirs by default
Change the default behavior of the klp test runner to save failing test
working directories instead of deleting them on failure. Provide a KEEP
Makefile variable that can optionally retain 'all' or 'none' of those
directories.
> diff --git a/tools/objtool/tests/lib.sh b/tools/objtool/tests/lib.sh
> index 4d8401ee8b412..6c607a0435023 100644
> --- a/tools/objtool/tests/lib.sh
> +++ b/tools/objtool/tests/lib.sh
[ ... ]
> @@ -186,12 +187,14 @@ cleanup()
> {
> [ -n "$workdir" ] || return 0
>
> - if [ -n "${KLP_TEST_KEEP:-}" ]; then
> - [ -n "${KLP_TEST_WORKDIR:-}" ] || echo "# kept $workdir"
> - return 0
> - fi
> -
> - rm -rf "$workdir"
[Severity: Medium]
When a test is executed standalone (not via run-tests.sh) and fails, does this
change silently leak the temporary directory without printing its path?
Before this patch, standalone test failures using KEEP=failed informed the
user of the generated /tmp directory path. Without the print statement,
developers might not be aware of the leaked directory location.
> + case "${KLP_TEST_KEEP:-failed}" in
> + all) return 0 ;;
> + none) rm -rf "$workdir" ;;
> + failed|*)
> + [ -n "${KLP_TEST_FAILED:-}" ] && return 0
> + rm -rf "$workdir"
[Severity: Medium]
If a test script exits unexpectedly without setting KLP_TEST_FAILED=1
(e.g., syntax error, shell error, or signal), will this incorrectly delete
the working directory despite KEEP=failed being set?
> + ;;
> + esac
> }
>
> # setup [exported symbol...]
> diff --git a/tools/objtool/tests/run-tests.sh b/tools/objtool/tests/run-tests.sh
> index e6f1ac1b5d0da..e7bd25097ea58 100755
> --- a/tools/objtool/tests/run-tests.sh
> +++ b/tools/objtool/tests/run-tests.sh
[ ... ]
> @@ -147,16 +162,16 @@ for t in "${tests[@]}"; do
> rest="$rest${rest:+$'\n'}was: $result"
> result="not ok - $(basename "$t" .sh): undeclared skip"
> result="$result (use gcc_only/clang_only or require_input_*)"
> - fail=$((fail + 1)) ;;
> + fail=$((fail + 1)); failed_dirs+=( "$rundir/${t%.sh}" ) ;;
> "not ok"*"# TODO"*) xfail=$((xfail + 1)) ;;
> - "ok"*"# TODO"*) xpass=$((xpass + 1)) ;;
> - "not ok"*) fail=$((fail + 1)) ;;
> + "ok"*"# TODO"*) xpass=$((xpass + 1)); failed_dirs+=( "$rundir/${t%.sh}" ) ;;
> + "not ok"*) fail=$((fail + 1)); failed_dirs+=( "$rundir/${t%.sh}" ) ;;
> "ok"*) pass=$((pass + 1)) ;;
> *)
> # No result line at all: the test died before reporting.
> rest="$rest${rest:+$'\n'}exited $rc without a result line"
> result="not ok - $(basename "$t" .sh): no TAP result"
> - fail=$((fail + 1)) ;;
> + fail=$((fail + 1)); failed_dirs+=( "$rundir/${t%.sh}" ) ;;
> esac
>
> echo "$result"
[ ... ]
> @@ -167,15 +182,35 @@ done
> echo "# pass:$pass fail:$fail static-skip:$static_skip" \
> "probe-skip:$probe_skip xfail:$xfail xpass:$xpass"
[ ... ]
> +failed)
> + if [ "${#failed_dirs[@]}" -gt 0 ]; then
> + echo "# keep=failed: ${#failed_dirs[@]} failing test(s) kept under $rundir:"
> + for d in "${failed_dirs[@]}"; do
> + echo "# ${d#"$rundir"/}/"
> + done
[Severity: Medium]
Will this instruct the user to inspect directories that have already been
wiped?
When a test crashes or skips without setting KLP_TEST_FAILED, the main loop in
run-tests.sh correctly detects this as a failure and adds it to failed_dirs.
However, cleanup() in lib.sh will have already deleted the directory because
KLP_TEST_FAILED is empty, leading to confusing instructions for the user.
> + echo "# inspect: diff.log readelf -S out.o"
> + echo "# one test: $PWD/run-tests.sh <name>"
> + echo "# cleanup: rm -rf $rundir"
> + elif ! rmdir "$rundir" 2>/dev/null; then
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260911185031.1534046-1-song@kernel.org?part=10
next prev parent reply other threads:[~2026-09-11 19:07 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 18:42 [PATCH 00/58] Unit test framework for klp-build toolchain Song Liu
2026-09-11 18:42 ` [PATCH 01/58] objtool: Add test harness for the klp subcommands Song Liu
2026-09-11 18:42 ` [PATCH 02/58] objtool/klp: Check the klp test environment once, before any test Song Liu
2026-09-11 19:02 ` sashiko-bot
2026-09-11 18:42 ` [PATCH 03/58] objtool/klp: Group the klp tests by architecture Song Liu
2026-09-11 18:42 ` [PATCH 04/58] objtool/klp: Classify klp test outcomes Song Liu
2026-09-11 18:42 ` [PATCH 05/58] objtool/klp: Build klp test fixtures through the harness Song Liu
2026-09-11 18:42 ` [PATCH 06/58] objtool/klp: Grow the klp test harness vocabulary Song Liu
2026-09-11 19:03 ` sashiko-bot
2026-09-11 18:42 ` [PATCH 07/58] objtool/klp: Give each run one working directory, one per test inside it Song Liu
2026-09-11 18:42 ` [PATCH 08/58] objtool/klp: Run the klp tests under set -u Song Liu
2026-09-11 18:42 ` [PATCH 09/58] objtool/klp: Document the klp test harness Song Liu
2026-09-11 19:00 ` sashiko-bot
2026-09-11 18:42 ` [PATCH 10/58] objtool: Keep failing test workdirs by default Song Liu
2026-09-11 19:07 ` sashiko-bot [this message]
2026-09-11 18:42 ` [PATCH 11/58] objtool: Forward toolchain variables to the klp test runner Song Liu
2026-09-11 18:42 ` [PATCH 12/58] objtool/klp: Add test for rejecting changed data Song Liu
2026-09-11 18:42 ` [PATCH 13/58] objtool/klp: Add test for newly introduced data Song Liu
2026-09-11 19:07 ` sashiko-bot
2026-09-11 18:42 ` [PATCH 14/58] objtool/klp: Add test for newly introduced functions Song Liu
2026-09-11 18:42 ` [PATCH 15/58] objtool/klp: Add test for static local correlation Song Liu
2026-09-11 18:42 ` [PATCH 16/58] objtool/klp: Add test for cold function halves Song Liu
2026-09-11 19:07 ` sashiko-bot
2026-09-11 18:42 ` [PATCH 17/58] objtool/klp: Add test for special section extraction Song Liu
2026-09-11 18:42 ` [PATCH 18/58] objtool/klp: Add test for selective " Song Liu
2026-09-11 18:42 ` [PATCH 19/58] objtool/klp: Add test for jump table key relocations Song Liu
2026-09-11 18:42 ` [PATCH 20/58] objtool/klp: Add test for rejecting module-owned static branch keys Song Liu
2026-09-11 18:42 ` [PATCH 21/58] objtool/klp: Add test for rejecting module-owned static call keys Song Liu
2026-09-11 18:42 ` [PATCH 22/58] objtool/klp: Add test for symids in discarded sections Song Liu
2026-09-11 18:42 ` [PATCH 23/58] objtool/klp: Add test for rejecting references to init code/data Song Liu
2026-09-11 19:18 ` sashiko-bot
2026-09-11 18:42 ` [PATCH 24/58] objtool/klp: Add test for correlation across ThinLTO name mangling Song Liu
2026-09-11 18:42 ` [PATCH 25/58] objtool/klp: Add test for objects without .modinfo Song Liu
2026-09-11 18:49 ` [PATCH 26/58] objtool/klp: Add test for unchecksummed input Song Liu
2026-09-11 18:50 ` [PATCH 27/58] objtool/klp: Add klp diff and post-link regression tests Song Liu
2026-09-11 18:50 ` [PATCH 28/58] objtool/klp: Add test for klp reloc section naming in module objects Song Liu
2026-09-11 18:50 ` [PATCH 29/58] objtool/klp: Add test for vmlinux relocs in a patched module Song Liu
2026-09-11 18:50 ` [PATCH 30/58] objtool/klp: Add test for Module.symvers path normalization Song Liu
2026-09-11 18:50 ` [PATCH 31/58] objtool/klp: Add test for the contents of the klp_funcs list Song Liu
2026-09-11 18:50 ` [PATCH 32/58] objtool/klp: Add test for EXPORT_SYMBOL_FOR_MODULES references Song Liu
2026-09-11 18:50 ` [PATCH 33/58] objtool/klp: Add test for new references to exported symbols Song Liu
2026-09-11 18:50 ` [PATCH 34/58] objtool/klp: Add test for empty x86 alternative replacements Song Liu
2026-09-11 18:50 ` [PATCH 35/58] objtool/klp: Add test for recorded checksum values Song Liu
2026-09-11 18:50 ` [PATCH 36/58] objtool/klp: Add test for position-independent checksums Song Liu
2026-09-11 19:16 ` sashiko-bot
2026-09-11 18:50 ` [PATCH 37/58] objtool/klp: Add test for sympos in module objects Song Liu
2026-09-11 19:21 ` sashiko-bot
2026-09-11 18:50 ` [PATCH 38/58] objtool/klp: Add test for sympos resolved against a linked vmlinux Song Liu
2026-09-11 18:50 ` [PATCH 39/58] objtool/klp: Add test for static locals which must not be correlated Song Liu
2026-09-11 18:50 ` [PATCH 40/58] objtool/klp: Add test for __bug_table, __ex_table and __mcount_loc extraction Song Liu
2026-09-11 19:20 ` sashiko-bot
2026-09-11 18:50 ` [PATCH 41/58] objtool/klp: Add test for kCFI prefix symbols and traps Song Liu
2026-09-11 19:21 ` sashiko-bot
2026-09-11 18:50 ` [PATCH 42/58] objtool/klp: Add test for symbols whose linkage the patch changes Song Liu
2026-09-11 18:50 ` [PATCH 43/58] objtool/klp: Test rejection of a file-local static branch key Song Liu
2026-09-11 18:50 ` [PATCH 44/58] objtool/klp: Test a hand-built livepatch module's static call keys Song Liu
2026-09-11 18:50 ` [PATCH 45/58] objtool/klp: Test text annotations on alternative replacements Song Liu
2026-09-11 18:50 ` [PATCH 46/58] objtool/klp: Add test for data object checksums Song Liu
2026-09-11 18:50 ` [PATCH 47/58] objtool/klp: Add test for symbols with no checksum entry of their own Song Liu
2026-09-11 19:23 ` sashiko-bot
2026-09-11 18:50 ` [PATCH 48/58] objtool/klp: Add test for a static branch introduced by the patch Song Liu
2026-09-11 18:50 ` [PATCH 49/58] objtool/klp: Add test for tracepoint and pr_debug static branch keys Song Liu
2026-09-11 18:50 ` [PATCH 50/58] objtool/klp: Add test for a static call introduced by the patch Song Liu
2026-09-11 19:25 ` sashiko-bot
2026-09-11 18:50 ` [PATCH 51/58] objtool/klp: Add test for instruction operand checksums Song Liu
2026-09-11 18:50 ` [PATCH 52/58] objtool/klp: Add test for alternative replacement code in checksums Song Liu
2026-09-11 19:30 ` sashiko-bot
2026-09-11 18:50 ` [PATCH 53/58] objtool/klp: Add test for the alignment of cloned data sections Song Liu
2026-09-11 18:50 ` [PATCH 54/58] objtool/klp: Add test for a patch which strips a data annotation Song Liu
2026-09-11 19:24 ` sashiko-bot
2026-09-11 18:50 ` [PATCH 55/58] objtool/klp: Add test for absolute and __ADDRESSABLE symbols Song Liu
2026-09-11 18:50 ` [PATCH 56/58] objtool/klp: Add test for UBSAN metadata in an unchanged function Song Liu
2026-09-11 18:50 ` [PATCH 57/58] objtool/klp: Add test for Clang switch jump tables Song Liu
2026-09-11 19:27 ` sashiko-bot
2026-09-11 18:50 ` [PATCH 58/58] objtool/klp: Add test for ThinLTO symbols sharing a demangled name Song Liu
2026-09-11 19:28 ` sashiko-bot
2026-09-13 1:53 ` [PATCH 00/58] Unit test framework for klp-build toolchain Josh Poimboeuf
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=20260911190705.248B91F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=kernel-team@meta.com \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=puranjay@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=song@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