|
From: David W. <we...@cw...> - 2002-05-19 14:09:51
|
On Sun, May 19, 2002 at 03:46:05PM +0200, Casper Hornstrup wrote: > Fixed, please try again. > I do not think this fix is correct; we can certainly try to lock an fast mutex when the current thread doesn't already own it but if the current thread does already own it then we will deadlock since fast mutexes aren't recursive. The real problem is locking the address space when we already own it so I had have reverted your changes and modified section.c not to do this. |