Displaying 20 results from an estimated 600 matches similar to: "[klibc:time64] select: Make all select calls wrappers for pselect6()"
2023 Jan 14
1
[klibc:time64] time: Use 64-bit time types on all architectures
Commit-ID: df7b02bd5c9af14c6efbe39ee4c313e368dfe967
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=df7b02bd5c9af14c6efbe39ee4c313e368dfe967
Author: Ben Hutchings <ben at decadent.org.uk>
AuthorDate: Sat, 14 Jan 2023 00:17:45 +0100
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 14 Jan 2023 18:10:12 +0100
[klibc] time: Use 64-bit time
2023 Jan 26
0
[klibc:time64] select: Fix handling of NULL timeout when wrapping pselect()
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
2013 Nov 08
0
[PATCH 2/3] syscalls: Add syscalls needed by arm64
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
2013 Nov 12
0
[klibc:master] syscalls: Add syscalls needed by arm64
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
2023 Jan 26
0
[klibc:time64] time: Use clock_* system calls for time-of-day and sleep
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
2013 Nov 12
0
[klibc:master] poll, select: fix style problems
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
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
Thanks for the interesting puzzle to crunch!
Looking at these few bread-crumbs, I wager an educated guess that this
loops in `sendcmd()` (where CLI child processes talk to a daemonized copy
which tracks the timers for events), around here:
https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626
for the daemon and here for the child:
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
Thanks for the interesting puzzle to crunch!
Looking at these few bread-crumbs, I wager an educated guess that this
loops in `sendcmd()` (where CLI child processes talk to a daemonized copy
which tracks the timers for events), around here:
https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626
for the daemon and here for the child:
2023 Jun 13
2
Upssched 100% CPU after updating Debian 12
FWIW, I wonder if this is a fallout of PR #1274 :
https://github.com/networkupstools/nut/pull/1274/files
and specifically
https://github.com/networkupstools/nut/commit/550064930e369fb3a322c3b28ffff8b4acf53532
which added a `sock_read()` loop continuation effectively if `pconf_char()`
returned 0.
Just grasping at straws here (since it is a change a couple of months
before the release was cut),
2023 Jun 13
2
Upssched 100% CPU after updating Debian 12
FWIW, I wonder if this is a fallout of PR #1274 :
https://github.com/networkupstools/nut/pull/1274/files
and specifically
https://github.com/networkupstools/nut/commit/550064930e369fb3a322c3b28ffff8b4acf53532
which added a `sock_read()` loop continuation effectively if `pconf_char()`
returned 0.
Just grasping at straws here (since it is a change a couple of months
before the release was cut),
2023 Jan 14
1
[klibc:time64] time: Use 64-bit time types on all architectures
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
2023 Jan 14
1
[klibc:time64] resource: Avoid using <linux/resource.h>
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
2023 Jan 14
1
[klibc:time64] resource: Avoid using <linux/resource.h>
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
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
Hi,
I ran the strace command while upssched was 100% CPU hungry. This is what I got:
1686633611.702798 read(7, "", 1) = 0 <0.000004>
1686633611.702816 read(7, "", 1) = 0 <0.000004>
1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006>
1686633611.702862 read(7,
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
Hi,
I ran the strace command while upssched was 100% CPU hungry. This is what I got:
1686633611.702798 read(7, "", 1) = 0 <0.000004>
1686633611.702816 read(7, "", 1) = 0 <0.000004>
1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006>
1686633611.702862 read(7,
2006 Apr 22
1
ia64 build failure - no fork or ppoll syscalls in 2.6.16
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.
2015 Mar 05
31
[Bug 2361] New: seccomp filter (not only) for aarch64
https://bugzilla.mindrot.org/show_bug.cgi?id=2361
Bug ID: 2361
Summary: seccomp filter (not only) for aarch64
Product: Portable OpenSSH
Version: 6.7p1
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: sshd
Assignee: unassigned-bugs at
2013 Feb 19
13
[PATCH] mini-os: implement poll(2)
It is just a wrapper around select(2).
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
extras/mini-os/include/posix/poll.h | 1 +
extras/mini-os/lib/sys.c | 90 ++++++++++++++++++++++++++++++++++-
2 files changed, 90 insertions(+), 1 deletion(-)
create mode 100644 extras/mini-os/include/posix/poll.h
diff --git a/extras/mini-os/include/posix/poll.h
2009 Nov 14
1
drivers- dynamically adding filedescriptors to poll
Recent work on the netxml-ups driver made me realize that it would be
very useful to be able to dynamically add/remove file descriptors we
want to monitor for activity (instead of just a single extrafd). We'll
probably also need this, in order to support asynchronous I/O in
libusb-1.0. The latter would be a huge improvement over the existing
libusb-0.1 (compatibility) interface
2020 Oct 14
2
Connection hang, can't stop SSH
Using OpenSSH_8.3p1 I had an open (working) connection to some other
box; after a bit of inactivity, some device in the middle seems to have
forgotten about the TCP connection (NAT) and broke it.
I've got an EscapeChar defined, though; so first I tried to send a BREAK
and, when that didn't help (TCP already gone, packets get lost!), I
tried (just out of curiosity) a Rekey.
Now I can see