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 <broonie@kernel.org>
Acked-by: Dev Jain <dev.jain@arm.com>
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

diff --git a/tools/testing/selftests/mm/mlock2-tests.c b/tools/testing/selftests/mm/mlock2-tests.c
index 7f0d50fa361dcf8726e46ef907a7b344e8cdc3bd..3e90ff37e336af2ed7f0127c6e1954ec74965873 100644 (file)
--- 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);
 }