+++ This bug was initially created as a clone of Bug #737387 +++
Created attachment 522617 [details]
test case demonstrating the issue
There appears to be a strange bug in glibc that causes deadlocks when calling fork() from threads. We had a testcase in GLib failing from time to time because of this.
I've attached a minimal testcase that uses only pure pthreads + libc. Compile it with -pthread and run it. It should fill your screen with dots for a while, then hang when it hits the bug (which happens randomly anywhere between 1 dot and hundreds). I've already received independent verification that this testcase hangs on several people's computers.
I believe this to be an upstream issue since this bug is visible on Ubuntu as well, but the glibc website says I should file bugs against distributions first. I also believe the issue to be a regression since older Fedora and RHEL releases are unaffected. The problem appears to affect both 32 and 64bits.
Description of problem:
- compiling the testcase with -static has the side-effect of causing the
bug to go away
- compiling the testcase with -DFORK_DIRECTLY also appears to solve the
- replacing the execv() with a direct exit(0) doesn't solve the problem
but causes the frequency to change
The fact that both static linking and making the fork() syscall directly cause the problem to disappear leads me to believe that this is a libc bug rather than a kernel bug (which is the only other possibility). I'm not 100% sure of that, though, since libc actually uses the clone() syscall to implement fork(), so there could be a different inside the kernel because of that.
We are hitting this bug regularly in RHEL5 (glibc 2.5). I have confirmed that the attached test case hangs on multiple machines.
Is there any chance of having the fix integrated into RHEL5?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.