On Wed, Jul 30, 2003 at 01:34:41PM -0500, William Rowe wrote: ... > Because the new patch protects the uninitalization of the mutex while > the lock is still held, the only failure scenario that remains is; > > 1. thread is interrupted (e.g. signal handler) in between the unsetting > of the ownership (and decrement of the refcount) and actually releasing > the mutex. The interrupt handler attempts to perform a nested lock > and deadlocks because the ownership has already been reset, but > the lock is not yet released.
Why are you worried about signal handlers using mutexes? Is httpd doing this somewhere?
