Review request for 5049299
aph at redhat.com
Tue Jun 23 07:33:36 PDT 2009
Martin Buchholz wrote:
> clone-exec update:
> I submitted the changes for this, but jtreg tests failed on 32-bit Linux
> (I had only tested on 64-bit Linux)
> We disabled (but did not roll back) the use of clone to allow the
> TL integration to proceed.
> (As I promised elsewhere...)
> I just filed a bug against upstream glibc demonstrating the problem
> with clone(CLONE_VM). You can see the small C program
> in my bug report below.
> Probably any discussion related just to the glibc bug
> can occur on the public glibc bugzilla at
> glibc maintainer Uli Drepper has already responded
> "If you use clone() you're on your own."
> so if we are going to fix it, we'll have to do it ourselves.
> Help from threading/kernel hackers appreciated.
I can debug this.
Please try first syscall(SYS_clone ...) to bypass the libc gubbins.
That might be all you need. If that doesn't help I'll have a look.
Isn't there some point at which you have to say to a Linux user "Your
system is simply misconfigured. Fix the overcommit parameter and this
problem will go away" ?
More information about the core-libs-dev