similar to: [PATCH 1/2] ia64: Fix invalid memory access in vfork

Commit 8418552 ("[klibc] ia64: Fix shared build") switched to the function descriptor-less ABI. However, when passing a function pointer to the kernel for signal handling, it always expects a descriptor, and -mno-pic does not set any ELF flags that the kernel could detect. Thus to fix this regression we must construct descriptors solely for passing to/from the kernel. Despite this,

Commit-ID: ae17951ae73ec52348c77259269637b854f0c236 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=ae17951ae73ec52348c77259269637b854f0c236 Author: Jessica Clarke <jrtc27 at jrtc27.com> AuthorDate: Fri, 28 Aug 2020 19:48:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 29 Aug 2020 17:23:08 +0100 [klibc] ia64: Fix sigaction

Commit-ID: 454901a0c733986bee36da111a08fe7df0ff0b98 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=454901a0c733986bee36da111a08fe7df0ff0b98 Author: Jessica Clarke <jrtc27 at jrtc27.com> AuthorDate: Fri, 28 Aug 2020 19:48:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 28 Aug 2020 20:22:50 +0100 [klibc] ia64: Fix sigaction struct

Commit-ID: 623b03fb63f0c0473b378cf61c77258fd450b5a1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=623b03fb63f0c0473b378cf61c77258fd450b5a1 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 28 Aug 2020 19:59:28 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 28 Aug 2020 20:22:50 +0100 [klibc] ia64: sigaction: Make

Commit-ID: 69fb0c9b936dd59a7f7c9fab40f9206b80837b5b Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=69fb0c9b936dd59a7f7c9fab40f9206b80837b5b Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 28 Aug 2020 19:59:28 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 29 Aug 2020 17:23:08 +0100 [klibc] ia64: sigaction: Make

From: Bradley Smith <brad at brad-smith.co.uk> This patch is from http://git.brad-smith.co.uk/?p=avr32/klibc.git;a=summary It squashes together and includes those commits: * Fix ld flags such that shared builds actually run. * Fix setjmp. * Fix sigaction/sigrestorer. * Tidy everything up. * Fix lseek mess. Cc: H?vard_Skinnemoen <hskinnemoen at gmail.com> Cc: Hans-Christian Egtvedt

Hi, is there a DD-accessible porterbox somewhere (slow would be ok, as this is smallish software) with an up-to-date sid (enough to install the recently-built libklibc-dev 2.0~rc5-1 and all other B-D of mksh 40.9.20120518-1, as well as strace and gdb-minimal)? Similarily to http://www.zytor.com/pipermail/klibc/2012-May/003229.html I found klibc-compiled programmes on Alpha to fail (SIGSEGV

I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at:

Commit-ID: faf48679047c91ac27dbb435d9189d0f0d59cb70 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=faf48679047c91ac27dbb435d9189d0f0d59cb70 Author: Jessica Clarke <jrtc27 at jrtc27.com> AuthorDate: Sat, 2 Feb 2019 02:29:47 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 29 Aug 2020 18:53:30 +0100 [klibc] ia64: Fix invalid memory

Commit-ID: cef709c42bb5ac1c45e7c42f440bc1c010f39b9b Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=cef709c42bb5ac1c45e7c42f440bc1c010f39b9b Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Sat, 19 May 2018 02:39:56 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: eval: Add vfork

The parts of klibc specific to the i386 architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit bd0599e5290ca1a16bb7a68f7c362d395c612eb3 tree 8f33afdd02a14c22e7a3984da2bad13184e3f729 parent 84f6a72f42cf41e32daa59871a0b5424572093e4 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:21 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

The parts of klibc specific to the x86_64 architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit f889dd04bef1aed36ba18161c727af47338e167a tree c25f184d2e3337b52dfe3abd191ec639d4d9543d parent f30fa3db62972125afa68d3b53d03cdb843d3bbd author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:53 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

The parts of klibc specific to the ia64 architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 951dc85bd690c6cc5a971815665da947160cbe51 tree 0843c8aa67a3c46a362d12c392c41c25d85ac9cd parent bd0599e5290ca1a16bb7a68f7c362d395c612eb3 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:24 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

Implement "pid_t vfork(void)" for parisc. Signed-off-by: Kyle McMartin <kyle at parisc-linux.org> --- Ugh. vfork() me harder. Kbuild | 2 +- vfork.S | 31 +++++++++++++++++++++++++++++++ 2 files changed, 32 insertions(+), 1 deletion(-) diff --git a/usr/klibc/arch/parisc/Kbuild b/usr/klibc/arch/parisc/Kbuild index d57a873..57ca5c2 100644 --- a/usr/klibc/arch/parisc/Kbuild

Commit-ID: b71dd57f6a784962681ac05aa686b28db8668609 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=b71dd57f6a784962681ac05aa686b28db8668609 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 21 Jan 2019 03:55:35 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Mon, 21 Jan 2019 03:55:35 +0000 [klibc] parisc: Fix vfork() The

Hi All, I has been trying to port the Samba package to uClinux. But our uClinux toolchain doesn't support the fork() call. I must replace the fork with vfork.If we use vfork, the smbd and nmbd can not work rightly. both samba-3.0.32 and samba-3.0.2a have the question. In samba/source/smbd/server.c, the function open_sockets_smbd(), creates a child process and a parent process. Both these

https://bugzilla.netfilter.org/show_bug.cgi?id=982 Bug ID: 982 Summary: vfork() in xtables.c can corrupt stack Product: iptables Version: 1.4.x Hardware: x86_64 OS: other Status: NEW Severity: normal Priority: P5 Component: iptables-restore Assignee: netfilter-buglog at

Hi klibc people, if someone has to say more on this, please do so. I?m only trying to explain what I _think_ I learned? >Begin forwarded message originally by Mike Frysinger: >> On Mon, Mar 21, 2011 at 10:24 AM, Waldemar Brodkorb wrote: >>> unfortunately the common vfork implementation, which just use >>> the syscall function to interact with the kernel, does not

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

Hello all, I really want to support vfork() in klibc, mostly because uClinux *has* to use it. Unfortunately vfork() isn't allowed to use the stack *at all* across the system call -- including return address -- which means it needs an assembly wrapper on most architectures. I have tried implementing wrappers for most architectures, but I don't know parisc or s390/s390x well enough,