From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] notify woe
Date: Wed, 7 Apr 2004 12:16:04 +1000 [thread overview]
Message-ID: <019f01c41c47$c8385fd0$8201a8c0@cc77109e> (raw)
In-Reply-To: <20040407014056.GA30936@mero.morphisms.net>
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.
brucee
----- Original Message -----
From: "William Josephson" <jkw@eecs.harvard.edu>
To: <9fans@cse.psu.edu>
Sent: Wednesday, April 07, 2004 11:40 AM
Subject: Re: [9fans] notify woe
> 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...
next prev parent reply other threads:[~2004-04-07 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 1:10 Bruce Ellis
2004-04-07 1:40 ` William Josephson
2004-04-07 2:16 ` Bruce Ellis [this message]
2004-04-07 3:28 ` William Josephson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='019f01c41c47$c8385fd0$8201a8c0@cc77109e' \
--to=brucee@chunder.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).