similar to: unbreak vfork on cris architecture

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

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

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,

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

The parts of klibc specific to the cris architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 84f6a72f42cf41e32daa59871a0b5424572093e4 tree 52bad10c1575f773a71cd4f4ea4b8083631f9d82 parent 1eff7c685b36cd0120694fd4150b32a26168d926 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:18 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

Commit-ID: a7a754c66437d4ab26503cdc183fd9e54a9e84d0 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=a7a754c66437d4ab26503cdc183fd9e54a9e84d0 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 30 Apr 2020 14:06:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 30 Apr 2020 14:08:28 +0100 [klibc] arch: Remove cris port

Hi all, I just built R from src on Windows 7 using Rtools212.exe. The build went as usual (R, bitmaps, and manuals all OK) but make check-all failed when running the examples for package 'tcltk': ... running code in 'demos2.R' ... OK running tests of primitives running code in 'primitives.R' ... OK make[2]: vfork: Resource temporarily unavailable make[1]: ***

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:

Hi, I?ve gone through the mailing list archives and hereby want to resubmit my pending patches. Most are independent of each other, except the m68k patch which will only be complete if sigsuspend is also fixed. (It can be applied before that, though.) http://www.zytor.com/pipermail/klibc/2012-January/003173.html [PATCH] fix m68k support Resubmitted here as 0005. While there was a question from

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

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

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

Commit 8418552 ("[klibc] ia64: Fix shared build") missed this use of the GP register, although the code appears to have been dubious anyway, assuming the address of errno was the first thing pointed to by GP. --- usr/klibc/arch/ia64/vfork.S | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/usr/klibc/arch/ia64/vfork.S b/usr/klibc/arch/ia64/vfork.S index

klibc now runs on the CRIS archtitecture. The patch below is against 0.146. Most of the changes are trivial but the new files in libgcc requires some comments. __negdi2.c: The CRIS port fallbacks to C-code for negdi2. The code in __negdi2.c is copied from libgcc2.c but with modified typenames. I would really appreciate if someone could check if it seams sane. crisarith.c: CRIS has no built-in

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

In preparation for the klibc 2.0.5 release I wrote a basic test script which: 1. Builds for each architecture (with a cross-compiler where needed) 2. Runs several statically-linked programs (using qemu-user where needed): a. Many self-test programs b. "sh -c exit" c. "sh -c '.../bin/true; exit'" The results for the architectures I was able to test are:

hello vorlon, got notified of your patch, will apply next days upstream unless some critiques are voiced on ml. thanks. -- maks ----- Forwarded message from Steve Langasek <steve.langasek at canonical.com> ----- Date: Wed, 16 Feb 2011 22:05:42 -0000 From: Steve Langasek <steve.langasek at canonical.com> Subject: [Bug 527720] Re: thumb2 porting issues identified: klibc uses

Hello- Shouldn't this catch swapcontext as well? Alistair On 26 May 2010, at 22:14, Dale Johannesen wrote: > > On May 26, 2010, at 2:05 PMPDT, Dan Gohman wrote: > >> vfork and getcontext have wildly platform-dependent semantics. >> Handling >> them conservatively is reasonable, even if some platforms don't need >> it. >> >> Dan >

I didn't see swapcontext in the list in gcc's special_function_p function... -bw On May 26, 2010, at 2:20 PM, Alistair Lynn wrote: > Hello- > > Shouldn't this catch swapcontext as well? > > Alistair > > On 26 May 2010, at 22:14, Dale Johannesen wrote: > >> >> On May 26, 2010, at 2:05 PMPDT, Dan Gohman wrote: >> >>> vfork and

tag 334917 = patch thanks Hi, I?ve fixed the m68k syscall of klibc and made it able to use six-argument syscalls like mmap2. However, I could not yet fully test it (only mostly; opendir() specifically fails) due to: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47533 @m68k porters: Please have a look at the gcc bug as well. @klibc: Please apply the patch, it?s better than what we have, and