selftests: vDSO: vdso_test_abi: Use UAPI system call numbers

SYS_clock_getres might have been redirected by libc to some other system
call than the actual clock_getres. For testing it is required to use
exactly this system call.

Use the system call number exported by the UAPI headers which is always
correct.

Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@kernel.org>
Link: https://patch.msgid.link/20251223-vdso-compat-time32-v1-3-97ea7a06a543@linutronix.de

diff --git a/tools/testing/selftests/vDSO/vdso_test_abi.c b/tools/testing/selftests/vDSO/vdso_test_abi.c
index c620317eaeea484c17c7c5c6a5f658a946794b7c..a75c12dcb0f1d4e65d6f754a10f010fcf28619e9 100644 (file)
--- a/tools/testing/selftests/vDSO/vdso_test_abi.c
+++ b/tools/testing/selftests/vDSO/vdso_test_abi.c
@@ -179,7 +179,7 @@ static void vdso_test_clock_getres(clockid_t clk_id)
                clock_getres_fail++;
        }
 
-       ret = syscall(SYS_clock_getres, clk_id, &sys_ts);
+       ret = syscall(__NR_clock_getres, clk_id, &sys_ts);
 
        ksft_print_msg("The syscall resolution is %lld %lld\n",
                        (long long)sys_ts.tv_sec, (long long)sys_ts.tv_nsec);