This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/18862] Cloning with CLONE_VFORK | CLONE_VM stops sending signals internally from working.
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 04 Sep 2015 10:39:54 +0000
- Subject: [Bug libc/18862] Cloning with CLONE_VFORK | CLONE_VM stops sending signals internally from working.
- Auto-submitted: auto-generated
- References: <bug-18862-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18862
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |fweimer at redhat dot com
Resolution|--- |INVALID
Flags| |security-
--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
fork_routine does not set up a glibc thread descriptor, and calling write and
_Exit corrupts the main thread descriptor. This means that the raise call
inside abort uses the wrong PID.
This is not a bug in glibc. If you call clone directly, you need to make sure
that you take care of the thread descriptor situation in some way.
--
You are receiving this mail because:
You are on the CC list for the bug.