This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/14499] Does posix_spawn invoke atfork handlers / use vfork?
- From: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Tue, 21 Aug 2012 13:43:08 +0000
- Subject: [Bug nptl/14499] Does posix_spawn invoke atfork handlers / use vfork?
- Auto-submitted: auto-generated
- References: <bug-14499-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14499
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #2 from Rich Felker <bugdal at aerifal dot cx> 2012-08-21 13:43:08 UTC ---
Indeed, while POSIX allows posix_spawn to call atfork handlers, this allowance
is only for the sake of implementations that can't avoid it. Calling them is
purely malevolent; it introduces opportunities for atfork-related race
conditions (like the infamous malloc/fork issue) and seriously degrades
performance by disallowing vfork and just from the overhead (usually heavy
synchronization overhead) in the atfork handlers.
Also, since posix_spawn is intended to be added to the list of
async-signal-safe functions in the next version of POSIX, this allowance is
surely going to vanish. It would benefit glibc to be ahead of the game and go
ahead and eliminate it.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.