From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue,  6 Apr 2004 23:28:55 -0400
From: William Josephson <jkw@eecs.harvard.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] notify woe
Message-ID: <20040407032855.GA31468@mero.morphisms.net>
References: <015701c41c3d$7c209770$8201a8c0@cc77109e> <20040407014056.GA30936@mero.morphisms.net> <019f01c41c47$c8385fd0$8201a8c0@cc77109e>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <019f01c41c47$c8385fd0$8201a8c0@cc77109e>
User-Agent: Mutt/1.4.2i
Topicbox-Message-UUID: 54018a68-eacd-11e9-9e20-41e7f4b1d025

On Wed, Apr 07, 2004 at 12:16:04PM +1000, Bruce Ellis wrote:
> i believe this bug to be simply that a (in this case single threaded)
> program is interrupted holding the malloc pool lock. the notify
> function indirectly calls malloc. sleep time.

Yep; that's the one (though I hit it somewhere inside
the thread scheduler and there's now a hack to mitigate
that particular instance).