From: Joerg Vehlow <lkml@jv-coder.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/aarch64: Remove 32 bit only syscalls
Date: Thu, 2 Sep 2021 11:36:55 +0200 [thread overview]
Message-ID: <20210902093655.6104-1-lkml@jv-coder.de> (raw)
From: Joerg Vehlow <joerg.vehlow@aox-tech.de>
These syscalls are not available in 64 bit builds of linux.
See: <linux>/include/uapi/asm-generic/unistd.h
With the syscall defined, the test clock_gettim04 fails with
../../../../include/tst_timer.h:216: TCONF: syscall(403) __NR_clock_gettime64 not supported
Fixes: 59d278d61ed90117607f389326e0816a14dbf53c ("lapi/syscalls: Update syscall numbers")
Signed-off-by: Joerg Vehlow <joerg.vehlow@aox-tech.de>
---
I am not 100% sure, how the syscall table for aarch64 is generated.
There are also compat version for some of the 32 bit only 64 bit syscalls,
but I think they are only available, when running an 32 bit arm application.
include/lapi/syscalls/aarch64.in | 20 --------------------
1 file changed, 20 deletions(-)
diff --git a/include/lapi/syscalls/aarch64.in b/include/lapi/syscalls/aarch64.in
index 5a2816099..a47185954 100644
--- a/include/lapi/syscalls/aarch64.in
+++ b/include/lapi/syscalls/aarch64.in
@@ -278,26 +278,6 @@ statx 291
io_pgetevents 292
rseq 293
kexec_file_load 294
-clock_gettime64 403
-clock_settime64 404
-clock_adjtime64 405
-clock_getres_time64 406
-clock_nanosleep_time64 407
-timer_gettime64 408
-timer_settime64 409
-timerfd_gettime64 410
-timerfd_settime64 411
-utimensat_time64 412
-pselect6_time64 413
-ppoll_time64 414
-io_pgetevents_time64 416
-recvmmsg_time64 417
-mq_timedsend_time64 418
-mq_timedreceive_time64 419
-semtimedop_time64 420
-rt_sigtimedwait_time64 421
-futex_time64 422
-sched_rr_get_interval_time64 423
pidfd_send_signal 424
io_uring_setup 425
io_uring_enter 426
--
2.25.1
next reply other threads:[~2021-09-02 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 9:36 Joerg Vehlow [this message]
2021-09-02 9:42 ` [LTP] [PATCH] syscalls/aarch64: Remove 32 bit only syscalls Viresh Kumar
2021-09-02 18:32 ` Arnd Bergmann
2021-09-03 4:33 ` Joerg Vehlow
2021-09-03 6:22 ` Petr Vorel
2021-09-03 11:03 ` Arnd Bergmann
2021-09-03 12:20 ` Petr Vorel
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=20210902093655.6104-1-lkml@jv-coder.de \
--to=lkml@jv-coder.de \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.