This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/4737] fork is not async-signal-safe
- From: "morten+sources dot redhat dot com at afdelingp dot dk" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 20 Oct 2008 11:46:17 -0000
- Subject: [Bug libc/4737] fork is not async-signal-safe
- References: <20070704013541.4737.nmiell@comcast.net>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From morten+sources dot redhat dot com at afdelingp dot dk 2008-10-20 11:46 -------
This bug in glibc is causing deadlocks in a server we are running.
The software follows the POSIX guidelines, and only calls "safe" functions
inside signal handlers. We've had no problems on BSD. On Linux (with glibc) the
software deadlocks once every few weeks, which is - of course - a total
show-stopper. We can't use Linux in the production environment if the software
keeps deadlocking.
I am no glibc hacker, and I am not sure how to fix this bug. If the locking is
needed, perhaps signals should be blocked while the lock is held?
Best regards,
Morten K. Poulsen
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4737
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.