[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openssh-bugs
Subject:    [Bug 3430] 64 bit time and seccomp conflict
From:       bugzilla-daemon () mindrot ! org
Date:       2022-05-09 11:32:46
Message-ID: bug-3430-705-va2jQu7HvR () https ! bugzilla ! mindrot ! org/
[Download RAW message or body]

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

--- Comment #7 from Darren Tucker <dtucker@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.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[prev in list] [next in list] [prev in thread] [next in thread]