From: Haofeng Li <lihaofeng@kylinos.cn>

Commit 57fbad15c2ee ("stackleak: Rename STACKLEAK to KSTACK_ERASE")
renamed the LKDTM crash type and selftest configuration but missed the
entry in tests.txt.

As a result, the selftest generates STACKLEAK_ERASING.sh, which run.sh
skips because the LKDTM DIRECT trigger only exposes KSTACK_ERASE. Rename
the test entry so the generated runner uses the registered crash type.

Fixes: 57fbad15c2ee ("stackleak: Rename STACKLEAK to KSTACK_ERASE")
Signed-off-by: Haofeng Li <lihaofeng@kylinos.cn>
---
 tools/testing/selftests/lkdtm/tests.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/lkdtm/tests.txt b/tools/testing/selftests/lkdtm/tests.txt
index d8180bbe31e8..bec57a02913a 100644
--- a/tools/testing/selftests/lkdtm/tests.txt
+++ b/tools/testing/selftests/lkdtm/tests.txt
@@ -78,7 +78,7 @@ USERCOPY_STACK_FRAME_TO
 USERCOPY_STACK_FRAME_FROM
 USERCOPY_STACK_BEYOND
 USERCOPY_KERNEL
-STACKLEAK_ERASING OK: the rest of the thread stack is properly erased
+KSTACK_ERASE OK: the rest of the thread stack is properly erased
 CFI_FORWARD_PROTO
 CFI_BACKWARD call trace:|ok: control flow unchanged
 FORTIFY_STRSCPY detected buffer overflow
-- 
2.25.1

On Wed, 15 Jul 2026 16:02:10 +0800, Haofeng Li wrote:
> Commit 57fbad15c2ee ("stackleak: Rename STACKLEAK to KSTACK_ERASE")
> renamed the LKDTM crash type and selftest configuration but missed the
> entry in tests.txt.
> 
> As a result, the selftest generates STACKLEAK_ERASING.sh, which run.sh
> skips because the LKDTM DIRECT trigger only exposes KSTACK_ERASE. Rename
> the test entry so the generated runner uses the registered crash type.
> 
> [...]

Applied to for-linus/hardening, thanks!

[1/1] selftests/lkdtm: rename STACKLEAK_ERASING to KSTACK_ERASE
      https://git.kernel.org/kees/c/b3a7aa9c0020

Take care,

-- 
Kees Cook