public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/14499] Does posix_spawn invoke atfork handlers / use vfork? Date: Tue, 21 Aug 2012 13:43:00 -0000 [thread overview] Message-ID: <bug-14499-131-u28AD340Yx@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <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.
next prev parent reply other threads:[~2012-08-21 13:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-20 22:24 [Bug nptl/14499] New: " luto at mit dot edu 2012-08-20 22:28 ` [Bug nptl/14499] " luto at mit dot edu 2012-08-21 13:43 ` bugdal at aerifal dot cx [this message] 2014-06-17 5:57 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-14499-131-u28AD340Yx@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).