[Bug 3430] 64 bit time and seccomp conflict

[bugzilla-daemon at mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=3430

Rustam Abdullaev <rustamabd at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rustamabd at gmail.com

--- Comment #10 from Rustam Abdullaev <rustamabd at gmail.com> ---
I've run into this issue on a 32-bit ARM platform with Ubuntu 22.04 and
kernel 6.1.36 (via buildroot).

Only the sshd seccomp fails with "SIGSYS, Bad system call". All other
invocations of clock_gettime work fine.

Core was generated by `sshd-session: [net]'.
Program terminated with signal SIGSYS, Bad system call.
#0  0xb6b349a6 in ?? () from /usr/lib/libc.so.6
#1  0xb6b95892 in __clock_gettime64 () from /usr/lib/libc.so.6
#2  0xb6b9593c in clock_gettime () from /usr/lib/libc.so.6
#3  0x00496b1c in ?? ()

Building with BR2_PACKAGE_OPENSSH_SANDBOX=n "fixes" the issue. So
there's definitely something wrong with seccomp on a 32-bit ARM
platform.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.