From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18627 invoked by alias); 20 Oct 2008 11:47:29 -0000 Received: (qmail 18491 invoked by uid 48); 20 Oct 2008 11:46:17 -0000 Date: Mon, 20 Oct 2008 11:47:00 -0000 Message-ID: <20081020114617.18490.qmail@sourceware.org> From: "morten+sources dot redhat dot com at afdelingp dot dk" To: glibc-bugs@sources.redhat.com In-Reply-To: <20070704013541.4737.nmiell@comcast.net> References: <20070704013541.4737.nmiell@comcast.net> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/4737] fork is not async-signal-safe X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2008-10/txt/msg00047.txt.bz2 ------- 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.