[Bug 3430] 64 bit time and seccomp conflict

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Mon May 9 21:32:46 AEST 2022


--- Comment #7 from Darren Tucker <dtucker at dtucker.net> ---
(In reply to Lacky from comment #6)
> Support for 64-bit time in 32 bit platforms has been added in kernel
> 5.1

The kernel version you're running should be irrelevant.  If you were
running the same binary on a kernel that had 64bit time you'd have the
same problem because the headers don't have __NR_clock_gettime64 and
thus sshd didn't add it to the filter.

> > What distro are you using?
> This is Buildroot-based Linux (https://buildroot.org/).

Sorry, I don't think there's anything OpenSSH could do differently. 
You've got a glibc that's making system calls that aren't in the
exported list of system calls.  I think your buildroot should be
defining __NR_clock_gettime64 if its glibc is going to call it.

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.

More information about the openssh-bugs mailing list