mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tip-bot2 for Thomas Weißschuh" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: thomas.weissschuh@linutronix.de,
	Thomas Gleixner <tglx@kernel.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: timers/vdso] selftests: vDSO: vdso_test_abi: Use UAPI system call numbers
Date: Tue, 13 Jan 2026 13:47:39 -0000	[thread overview]
Message-ID: <176831205991.510.5977880468527402568.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20251223-vdso-compat-time32-v1-3-97ea7a06a543@linutronix.de>

The following commit has been merged into the timers/vdso branch of tip:

Commit-ID:     1dcd1273add368c2b7c65135e22b416e1b374781
Gitweb:        https://git.kernel.org/tip/1dcd1273add368c2b7c65135e22b416e1b374781
Author:        Thomas Weißschuh <thomas.weissschuh@linutronix.de>
AuthorDate:    Tue, 23 Dec 2025 07:59:14 +01:00
Committer:     Thomas Gleixner <tglx@kernel.org>
CommitterDate: Tue, 13 Jan 2026 14:42:23 +01:00

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
---
 tools/testing/selftests/vDSO/vdso_test_abi.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/vDSO/vdso_test_abi.c b/tools/testing/selftests/vDSO/vdso_test_abi.c
index c620317..a75c12d 100644
--- 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);

  reply	other threads:[~2026-01-13 13:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-23  6:59 [PATCH 0/9] vDSO: Provide clock_getres_time64() where applicable Thomas Weißschuh
2025-12-23  6:59 ` [PATCH 1/9] vdso: Add prototype for __vdso_clock_getres_time64() Thomas Weißschuh
2026-01-13 13:47   ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-12-23  6:59 ` [PATCH 2/9] selftests: vDSO: vdso_config: Add configurations for clock_getres_time64() Thomas Weißschuh
2026-01-13 13:47   ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-12-23  6:59 ` [PATCH 3/9] selftests: vDSO: vdso_test_abi: Use UAPI system call numbers Thomas Weißschuh
2026-01-13 13:47   ` tip-bot2 for Thomas Weißschuh [this message]
2025-12-23  6:59 ` [PATCH 4/9] selftests: vDSO: vdso_test_abi: Add test for clock_getres_time64() Thomas Weißschuh
2026-01-13 13:47   ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-12-23  6:59 ` [PATCH 5/9] x86/vdso: Provide clock_getres_time64() for x86-32 Thomas Weißschuh
2026-01-13 13:47   ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-12-23  6:59 ` [PATCH 6/9] ARM: VDSO: also patch out __vdso_clock_getres() if unavailable Thomas Weißschuh
2026-01-13 13:47   ` [tip: timers/vdso] ARM: VDSO: Patch " tip-bot2 for Thomas Weißschuh
2025-12-23  6:59 ` [PATCH 7/9] ARM: VDSO: provide clock_getres_time64() Thomas Weißschuh
2026-01-13 13:47   ` [tip: timers/vdso] ARM: VDSO: Provide clock_getres_time64() tip-bot2 for Thomas Weißschuh
2025-12-23  6:59 ` [PATCH 8/9] arm64: vdso32: " Thomas Weißschuh
2026-01-05 20:55   ` Will Deacon
2026-01-13 13:47   ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-12-23  6:59 ` [PATCH 9/9] MIPS: vdso: Provide getres_time64() for 32-bit ABIs Thomas Weißschuh
2026-01-13 13:47   ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh

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=176831205991.510.5977880468527402568.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=tglx@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=x86@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

all inboxes | Powered by JetHome®