search for: clock_gettime64

...quot;..., 35 Sharename?????? Type????? Comment ) = 35 0.000883 write(1, "\t---------?????? ----????? -----"..., 35 ---------?????? ----????? ------- ) = 35 0.000466 epoll_create(64)????????? = 3 0.000873 fcntl64(3, F_GETFD)?????? = 0 0.000318 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 0.000890 clock_gettime64(CLOCK_REALTIME, {tv_sec=1730806466, tv_nsec=500839090}) = 0 0.000555 clock_gettime64(CLOCK_REALTIME, {tv_sec=1730806466, tv_nsec=501842685}) = 0 0.000997 epoll_ctl(3, EPOLL_CTL_ADD, 5, {events=EPOLLIN|EPOLLERR|EPOLLHUP, data={u32=37735016, u64=37735016}}) = 0 0.000889 writev(5, [{iov_base="...

On Tue, 5 Nov 2024 10:36:49 +0100 Gilles via samba <samba at lists.samba.org> wrote: > On 04/11/2024 15:11, Rowland Penny via samba wrote: > > As I said previously, I do not think this has anything to do with > > Samba. In an earlier post, you had this output when you ran the same > > command using 'time': > > > > real 0m12.500s > > user

...bug3: mm_request_receive: entering debug1: do_cleanup debug1: Killing privsep child 528 ... The last defined system call in <asm/unistd-common.h> is __NR_io_pgetevents, 399. According to this URL, https://gpages.juszkiewicz.com.pl/syscalls-table/syscalls.html, system call 403 is clock_gettime64 in Arm32. clock_gettime64 is not defined for the older Digi DEY 8.2.0 toolchain that does work with OpenSSH: % grep -r clock_gettime64 /opt/sysroots/cortexa9t2hf-neon-dey-linux-gnueabi/ /opt/sysroots/x86_64-deysdk-linux/ but is defined for Arm GNU Toolchain 12.3.1 (and 11.3.1 and 10.3-2021.0...

...time. OpenSSH in source code tries to figure which syscalls are supported by kernel and only supported syscalls are added as an allowed in seccomp (https://github.com/openssh/openssh-portable/blob/master/sandbox-seccomp-filter.c). Because kernel 4.14 doesn?t support syscalls for 64 bit time, __NR_clock_gettime64 is not added as a trusted syscall to seccomp. As a result OpenSSH process is killed by seccomp every time when it tries to use clock_gettime from glibc. -- You are receiving this mail because: You are watching the assignee of the bug.

...y.c > arch/mips/vdso/gettimeofday.c > arch/arm/vdso/vgettimeofday.c > > are basically all minor variations of the same code base and could be > consolidated to some degree. > Any suggestions here? Should we plan to do that consolitdation based on > your new version, or just add clock_gettime64 in arm32 and x86-32, and then > be done with it? The other ones will obviously still be fast for 32-bit time_t > and will have a working non-vdso sys_clock_getttime64(). In principle consolidating all those implementations should be possible to some extent and probably worthwhile. What's...

...arch/nds32/kernel/vdso/gettimeofday.c arch/mips/vdso/gettimeofday.c arch/arm/vdso/vgettimeofday.c are basically all minor variations of the same code base and could be consolidated to some degree. Any suggestions here? Should we plan to do that consolitdation based on your new version, or just add clock_gettime64 in arm32 and x86-32, and then be done with it? The other ones will obviously still be fast for 32-bit time_t and will have a working non-vdso sys_clock_getttime64(). I also wonder about clock_getres(): half the architectures seem to implement it in vdso, but notably arm32 and x86 don't, and I...

...); int settimeofday::__settimeofday(const void *, const struct timezone *); -int clock_gettime(clockid_t, struct timespec *); -int clock_settime(clockid_t, const struct timespec *); -int clock_nanosleep::__clock_nanosleep(clockid_t, int, const struct timespec *, struct timespec *); +<32> int clock_gettime64::clock_gettime(clockid_t, struct timespec *); +<64> int clock_gettime(clockid_t, struct timespec *); +<32> int clock_settime64::clock_settime(clockid_t, const struct timespec *); +<64> int clock_settime(clockid_t, const struct timespec *); +<32> int clock_nanosleep_time64::_...

...d a banner (e.g. multiplexers like sslh) * sshd_config(5): document the sntrup4591761x25519-sha512 at tinyssh.org key exchange algorithm. PR#151 Portability ----------- * sshd(8): multiple adjustments to the Linux seccomp sandbox: - Non-fatally deny IPC syscalls in sandbox - Allow clock_gettime64() in sandbox (MIPS / glibc >= 2.31) - Allow clock_nanosleep_time64 in sandbox (ARM) bz3100 - Allow clock_nanosleep() in sandbox (recent glibc) bz3093 * Explicit check for memmem declaration and fix up declaration if the system headers lack it. bz3102 Checksums: ========== - SHA1 (...

...d a banner (e.g. multiplexers like sslh) * sshd_config(5): document the sntrup4591761x25519-sha512 at tinyssh.org key exchange algorithm. PR#151 Portability ----------- * sshd(8): multiple adjustments to the Linux seccomp sandbox: - Non-fatally deny IPC syscalls in sandbox - Allow clock_gettime64() in sandbox (MIPS / glibc >= 2.31) - Allow clock_nanosleep_time64 in sandbox (ARM) bz3100 - Allow clock_nanosleep() in sandbox (recent glibc) bz3093 * Explicit check for memmem declaration and fix up declaration if the system headers lack it. bz3102 Checksums: ========== - SHA1 (...

...d a banner (e.g. multiplexers like sslh) * sshd_config(5): document the sntrup4591761x25519-sha512 at tinyssh.org key exchange algorithm. PR#151 Portability ----------- * sshd(8): multiple adjustments to the Linux seccomp sandbox: - Non-fatally deny IPC syscalls in sandbox - Allow clock_gettime64() in sandbox (MIPS / glibc >= 2.31) - Allow clock_nanosleep_time64 in sandbox (ARM) bz3100 - Allow clock_nanosleep() in sandbox (recent glibc) bz3093 * Explicit check for memmem declaration and fix up declaration if the system headers lack it. bz3102 Checksums: ========== - SHA1 (...

Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime() implementation, which extended the clockid switch case and added yet another slightly different copy of the same code. Especially the extended switch case is problematic as the compiler tends to generate a jump table which then requires to use retpolines. If jump tables are disabled it adds yet another conditional to the existing

Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime() implementation, which extended the clockid switch case and added yet another slightly different copy of the same code. Especially the extended switch case is problematic as the compiler tends to generate a jump table which then requires to use retpolines. If jump tables are disabled it adds yet another conditional to the existing

...d a banner (e.g. multiplexers like sslh) * sshd_config(5): document the sntrup4591761x25519-sha512 at tinyssh.org key exchange algorithm. PR#151 Portability ----------- * sshd(8): multiple adjustments to the Linux seccomp sandbox: - Non-fatally deny IPC syscalls in sandbox - Allow clock_gettime64() in sandbox (MIPS / glibc >= 2.31) - Allow clock_nanosleep_time64 in sandbox (ARM) bz3100 - Allow clock_nanosleep() in sandbox (recent glibc) bz3093 * Explicit check for memmem declaration and fix up declaration if the system headers lack it. bz3102 OpenSSH is brought to you by Mar...