[Buildroot] [Bug 14796] 64 bit time and seccomp conflict (OpenSSH server crash)

[bugzilla@busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=14796

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Peter Korsgaard and I finally had a look at this today, and we think we finally
understand what is going on.

glibc does not care about the kernel headers when deciding whether to use the
clock_gettime64() syscall or not: it always use it, and if that fails at
runtime, it falls back to clock_gettime(). This is how glibc ends up using
clock_gettime64() even if your kernel does not support it.

On the other hand, the OpenSSL seccomp code relies on kernel headers to decide
whether the clock_gettime64() syscall should be in the allowed list of syscalls
or not.

So when you are in a situation where glibc is recent, but your kernel is older,
you get into precisely the problem you have: glibc tries to use
clock_gettime64, but OpenSSH seccomp configuration prevents that, which does
not allow glibc to gracefully fallback to clock_gettime.

The only solution that we see is to disable seccomp support in OpenSSH. Peter
will send a patch for this. I will keep this bug open until this patch is
posted and hopefully merged.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot