Repository navigation
Conversation
On 32-bit architectures with a 64-bit time_t ABI (Linux 5.1 and later) libc and the Go runtime call the *_time64 syscalls instead of the 32-bit time ones; Go uses futex_time64 once the kernel is new enough. The default profile only lists the old names, so its default errno action denies futex_time64 and the runtimetest binary aborts inside the container on i386, arm and mips. Allow the time64 variant of every syscall the profile already allows. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
dangowrt
marked this pull request as ready for review
October 20, 2026 19:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On 32-bit architectures Linux 5.1 added
*_time64variants of every syscall that takes atime_t, and libc and the Go runtime switch to them on such kernels. Go usesfutex_time64once the kernel is 5.1 or newer (runtime/os_linux32.go). The default seccomp profile only lists the old names, so its defaultSCMP_ACT_ERRNOaction deniesfutex_time64;runtimetestaborts inside the container (futexwakeup ... returned -1, then a deliberateSIGSEGV) and every test that runs it reports nothing on i386, arm and mips.This adds the time64 variant of every syscall the profile already allows:
clock_gettime64,clock_getres_time64,clock_nanosleep_time64,futex_time64,mq_timedreceive_time64,mq_timedsend_time64,ppoll_time64,pselect6_time64,recvmmsg_time64,rt_sigtimedwait_time64,sched_rr_get_interval_time64,semtimedop_time64,timer_gettime64,timer_settime64,timerfd_gettime64,timerfd_settime64andutimensat_time64.clock_settime,clock_adjtimeandio_pgeteventsare not in the profile, so their variants are not added either.Tested with an i386 OpenWrt image (kernel 6.18) running the validation suite against a runtime that enforces the profile: the suite goes from 388 to 3497 passing assertions; amd64 is unaffected.