similar to: [klibc:time64] time: Use 64-bit time types on all architectures

Commit-ID: 8b44cc180f664532821211e8261534b0c9e6c01c Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8b44cc180f664532821211e8261534b0c9e6c01c Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 14 Jan 2023 02:15:10 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 15 Jan 2023 21:28:18 +0100 [klibc] time: Use clock_* system

Commit-ID: 567944d04b7a94c7518857f518378191f6bb4046 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=567944d04b7a94c7518857f518378191f6bb4046 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 14 Jan 2023 02:10:01 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 15 Jan 2023 21:28:18 +0100 [klibc] select: Make all select

On Sat, Jan 14, 2023, at 23:03, klibc-bot for Ben Hutchings wrote: > > #include <klibc/extern.h> > +#include <klibc/endian.h> > #include <stddef.h> > #include <sys/types.h> > -#include <linux/time.h> > + > +struct timespec { > + __kernel_time64_t tv_sec; > +#if __BYTE_ORDER == __BIG_ENDIAN && __BITS_PER_LONG == 32 > + long

Commit-ID: d4ab7343978bbec7141f8462236ba6a47574205f Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=d4ab7343978bbec7141f8462236ba6a47574205f Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 14 Jan 2023 03:15:20 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 14 Jan 2023 18:09:28 +0100 [klibc] resource: Avoid using

Commit-ID: fcbb80e223c369467680536b71c781918e614219 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=fcbb80e223c369467680536b71c781918e614219 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 14 Jan 2023 03:43:16 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 15 Jan 2023 21:28:18 +0100 [klibc] select: Fix handling of

arm64 uses generic syscalls, and does not include the "noat", "noflags", and "deprecated" syscalls. i.e. __ARCH_WANT_SYSCALL_{NO_AT|NO_FLAGS|DEPRECATED} This patch adds the syscalls needed for klibc to run on arm64. Signed-off-by: Steve Capper <steve.capper at linaro.org> --- usr/klibc/Kbuild | 3 +++ usr/klibc/SYSCALLS.def | 33

Commit-ID: 8858e8319655ef38398e0833b71d65b0e620a061 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8858e8319655ef38398e0833b71d65b0e620a061 Author: Steve Capper <steve.capper at linaro.org> AuthorDate: Mon, 11 Nov 2013 17:04:11 +0000 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:31:13 -0800 [klibc] syscalls: Add syscalls

Commit-ID: 3892f676f83d4da24f6417846645272d367a97a7 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=3892f676f83d4da24f6417846645272d367a97a7 Author: H. Peter Anvin <hpa at zytor.com> AuthorDate: Mon, 11 Nov 2013 19:48:04 -0800 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:48:04 -0800 [klibc] poll, select: fix style problems

klibc fails to build on ia64 because it has neither fork nor the ppoll syscalls. This patch marks the former in SYSCALLS.def, and puts a guard wrapper around the ppoll definition in ppoll.c Should these calls return ENOSYS rather than simply not existing on some systems? If yes, please apply this and I'll follow up with a patch shortly that does ENOSYS for this and pselect at least.

In the patch series I posted recently [1], I introduce new system calls to deal with modified data structures, but left the question open on how these should be best accessed from libc. The patches introduce a new __kernel_time64_t type and based on that five new data structured: struct __kernel_timespec, struct __kernel_itimerspec, struct __kernel_stat, struct __kernel_rusage, and struct

On Sat, Jan 14, 2023, at 23:03, klibc-bot for Ben Hutchings wrote: > Commit-ID: d4ab7343978bbec7141f8462236ba6a47574205f > Gitweb: > http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=d4ab7343978bbec7141f8462236ba6a47574205f > Author: Ben Hutchings <ben at decadent.org.uk> > AuthorDate: Sat, 14 Jan 2023 03:15:20 +0100 > Committer: Ben Hutchings <ben at

On Nov 2, 2023, at 4:39 PM, Grant Erickson <gerickson at nuovations.com> wrote: > On Nov 2, 2023, at 4:32 PM, Damien Miller <djm at mindrot.org> wrote: >> On Mon, 30 Oct 2023, Grant Erickson wrote: >> >>> I have an NXP i.MX6-based armv7l-dey-linux-gnueabihf system in which I >>> am seeing some as-yet-unaccountable behavior in sshd when compiled with

configure uses clock_gettime to check whether -lrt is needed - and don''t check other functions. With glibc 2.17 clock_gettime is part of libc, so use timer_gettime instead, which is in -lrt in old and new versions of glibc. Signed-off-by: Olaf Hering <olaf@aepfle.de> --- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure b/configure index

On 05/18/2015 02:53 AM, Arnd Bergmann wrote: > In the patch series I posted recently [1], I introduce new system calls to deal > with modified data structures, but left the question open on how these should > be best accessed from libc. The patches introduce a new __kernel_time64_t type > and based on that five new data structured: struct __kernel_timespec, > struct

The code flow for the vclocks is convoluted as it requires the vclocks which can be invalidated separately from the vsyscall_gtod_data sequence to store the fact in a separate variable. That's inefficient. Restructure the code so the vclock readout returns cycles and the conversion to nanoseconds is handled at the call site. If the clock gets invalidated or vclock is already VCLOCK_NONE,

On Monday 18 May 2015 12:16:48 Thorsten Glaser wrote: > Arnd Bergmann dixit: > > >In the patch series I posted recently [1], I introduce new system calls to deal > >with modified data structures, but left the question open on how these should > >be best accessed from libc. The patches introduce a new __kernel_time64_t type > > Can we please have ioctls fixed for

On Wed, May 1, 2013 at 09:21:17AM -0700, Matt Wilson wrote: > On Mon, Apr 29, 2013 at 03:40:13PM +0200, Olaf Hering wrote: > > Ping > > Makes sense. > > Acked-by: Matt Wilson <msw@amazon.com> > > > On Wed, Jan 16, Olaf Hering wrote: > > > > > Ping > > > > > > On Wed, Dec 05, Olaf Hering wrote: > > > > > > >

Hello, The 2.6.12-xenU kernel does not seem to have smbfs support. I couldn''t find the config files for it so maybe I''m missing something obvious, but I read that you need to compile your own kernel to get smbfs support. I''m trying to follow the guide at http://www.debian-administration.org/articles/320 I''ve done exactly as the guide says, except

Hi All! I use on my debian stable hosts here only sernet pkgs with samba 3.0.32. It works perfectly with Windows 2008 ADS. On my unstble host I have the 'standard' debian sid pkgs with samba 3.2.3. I have there a problem. It does work 45min - 1h and then I get this error with wbinfo -t: checking the trust secret via RPC calls failed error code was NT_STATUS_DOMAIN_CONTROLLER_NOT_FOUND

Commit-ID: 0dbcedacde2847e254373fce6f80c63e003a69ca Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0dbcedacde2847e254373fce6f80c63e003a69ca Author: Colin Watson <cjwatson at ubuntu.com> AuthorDate: Tue, 25 Sep 2012 12:31:16 +0100 Committer: maximilian attems <max at stro.at> CommitDate: Mon, 1 Oct 2012 15:04:49 +0200 [klibc] include: [sys/time.h] fix for