similar to: ia64 build failure - no fork or ppoll syscalls in 2.6.16

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

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

It is necessary to kick the state machine any time another thread blocks due to write() encountering a full buffer, to get the reader thread to learn that it must now poll on POLLOUT rather than just POLLIN. POSIX only provides two ways to do this: either poll() on a second fd (our pipe-to-self trick), or interrupt the polling with EINTR due to delivery of a signal. So, I played with the latter

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

We noticed while writing various libnbd tests that when the delay filter is in use, there are scenarios where we had to resort to SIGKILL to get rid of nbdkit, because it was non-responsive to SIGINT. I'm still trying to figure out the best way to add testsuite coverage of this, but already proved to myself that it works from the command line, under two scenarios that both used to cause long

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

On Wed, Oct 15, 2014 at 12:23:17PM +0000, VONDRA Alain wrote: > Now, the conversion hangs on the first disk at 54,03/100%, here is the gdb result : OK I just talked to Paolo about this, and it's fairly serious. Can you get a core dump from this? You will need to set up the ulimit etc as outlined in the previous email: https://www.redhat.com/archives/libguestfs/2014-October/msg00102.html

Now, the conversion hangs on the first disk at 54,03/100%, here is the gdb result : (gdb) t a a bt Thread 2 (Thread 0x7f0f3cea9700 (LWP 9583)): #0 sem_timedwait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101 #1 0x00007f0f45b765e7 in qemu_sem_timedwait () #2 0x00007f0f45b0750c in worker_thread () #3 0x00007f0f4203bdf3 in start_thread (arg=0x7f0f3cea9700) at

There are a couple of problems with filters trying to sleep. First, when it is time to shut down nbdkit, we wait until all pending transactions have had a chance to wind down. But consider what happens if one or more of those pending transactions are blocked in a sleep. POSIX says nanosleep is interrupted with EINTR if that thread handles a signal, but wiring up signal masks just to ensure a

Killall does nothing the process is still alive... If I do kill -9, do I get a core dump ? Each time I got this hang, I find only umount -f /tmp/xxxx to force qemu-img to stop. Alain -----Message d'origine----- De : Richard W.M. Jones [mailto:rjones@redhat.com] Envoyé : mercredi 15 octobre 2014 14:41 À : VONDRA Alain Cc : libguestfs@redhat.com Objet : Re: [Libguestfs] Virt-v2v conversion

https://bugs.freedesktop.org/show_bug.cgi?id=93197 Bug ID: 93197 Summary: Warsow 2.0 crashes in nouveau_fence_trigger_work Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau Assignee:

comments? alternatives: sigsetjmp(ugly) and pselect(not portable, available) drawback: additional filedescriptors. Index: serverloop.c =================================================================== RCS file: /home/markus/cvs/ssh/serverloop.c,v retrieving revision 1.82 diff -u -r1.82 serverloop.c --- serverloop.c 10 Oct 2001 22:18:47 -0000 1.82 +++ serverloop.c 11 Oct 2001 18:06:33 -0000 @@

Commit-ID: 75895304280f597f46551deb8b87c27ac18a013c Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=75895304280f597f46551deb8b87c27ac18a013c Author: Helge Deller <deller at gmx.de> AuthorDate: Wed, 6 Jan 2016 00:43:50 +0000 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Tue, 5 Jan 2016 17:45:50 -0800 [klibc] Add pread and pwrite 32bit syscall

Rather than failing to compile on platforms which lack POLLRDHUP such as FreeBSD, simply fallback to the old method of sleeping. This leaves the porting suggestions as a comment in case someone wants to implement a better solution for particular platforms. --- server/public.c | 38 ++++++++++++++++++++++++-------------- 1 file changed, 24 insertions(+), 14 deletions(-) diff --git

https://bugzilla.mindrot.org/show_bug.cgi?id=3531 Bug ID: 3531 Summary: Ssh will not exit when it receives SIGTERM before calling poll in client_wait_until_can_do_something until some events happen. Product: Portable OpenSSH Version: 9.1p1 Hardware: Other OS: Linux Status:

Hi, tinc has a fixed timeout of 1 second for select() in the main loop. I think this could be improved. Do you think the following patch goes into the right direction ? I don't know whether pselect() is standard enough (works under "current" linux, however I don't know about the other arches). Maybe a config option is necessary. It's probably possible

On Tue, Oct 14, 2014 at 03:40:22PM +0000, VONDRA Alain wrote: > Rich, > I've followed your instructions to trace, but I am not very skilful with gdb, maybe I made a mistake : > > (1) As root do: > > echo core.%p > /proc/sys/kernel/core_pattern -> OK > > (2) Before running virt-v2v, do: > > ulimited -c unlimited -> I think it's

Newer udev versions asks for it: libudev/libudev-util.c:168:12: warning: incompatible implicit declaration of built-in function 'mempcpy' [enabled by default] Signed-off-by: maximilian attems <max at stro.at> --- usr/include/string.h | 1 + usr/klibc/Kbuild | 2 +- usr/klibc/mempcpy.c | 7 +++++++ 3 files changed, 9 insertions(+), 1 deletions(-) create mode 100644

On Sun, May 21, 2023 at 09:51:24PM -0500, Mike Christie wrote: > When switching from kthreads to vhost_tasks two bugs were added: > 1. The vhost worker tasks's now show up as processes so scripts doing ps > or ps a would not incorrectly detect the vhost task as another process. > 2. kthreads disabled freeze by setting PF_NOFREEZE, but vhost tasks's > didn't disable or

From: Heiko Carstens <heiko.carstens@de.ibm.com> vfork support for s390/s390x. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> --- diff -purN a/usr/klibc/SYSCALLS.def b/usr/klibc/SYSCALLS.def --- a/usr/klibc/SYSCALLS.def 2006-06-07 09:44:33.000000000 +0200 +++ b/usr/klibc/SYSCALLS.def 2006-06-07 13:01:54.000000000 +0200 @@ -28,7 +28,7 @@ void _exit,exit::_exit(int) ; A