From: Mark Brown Date: Thu, 15 May 2025 09:27:14 +0000 (+0200) Subject: selftests/mm: deduplicate test logging in test_mlock_lock() X-Git-Tag: v6.16-rc1~73^2~36 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=62973e38670a660480ab19c9241f8d77e89b0199;p=thirdparty%2Fkernel%2Flinux.git selftests/mm: deduplicate test logging in test_mlock_lock() The mlock2-tests test_mlock_lock() test reports two test results with an identical string, one reporitng if it successfully locked a block of memory and another reporting if the lock is still present after doing an unlock (following a similar pattern to other tests in the same program). This confuses test automation since the test string is used to deduplicate tests, change the post unlock test to report "Unlocked" instead like the other tests to fix this. Link: https://lkml.kernel.org/r/20250515-selftest-mm-mlock2-dup-v1-1-963d5d7d243a@kernel.org Signed-off-by: Mark Brown Acked-by: Dev Jain Cc: Shuah Khan Signed-off-by: Andrew Morton --- diff --git a/tools/testing/selftests/mm/mlock2-tests.c b/tools/testing/selftests/mm/mlock2-tests.c index 7f0d50fa361dc..3e90ff37e336a 100644 --- a/tools/testing/selftests/mm/mlock2-tests.c +++ b/tools/testing/selftests/mm/mlock2-tests.c @@ -196,7 +196,7 @@ static void test_mlock_lock(void) ksft_exit_fail_msg("munlock(): %s\n", strerror(errno)); } - ksft_test_result(!unlock_lock_check(map), "%s: Locked\n", __func__); + ksft_test_result(!unlock_lock_check(map), "%s: Unlocked\n", __func__); munmap(map, 2 * page_size); }