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

On Wed, Apr 07, 2004 at 11:10:38AM +1000, Bruce Ellis wrote:
> gee, don't call malloc from a notify function, this is from mk ...
> 
> actually don't call wait, or any library function that allocates,
> from a notify function.  how's my timing in interrupting a malloc?

I seem to recall stumbling over that one a year or two
ago and mentioning it to the list or 9trouble.  Actually,
I think it was a race for the malloc lock, perhaps, that
could cause a deadlock in the thread library at interrupt
time.  Similar issue in any case...