From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] infrequent panics
Date: Wed, 12 Mar 2008 22:14:31 -0400 [thread overview]
Message-ID: <b71045ceaf4a0a7dc26c04e459088ad8@quanstro.net> (raw)
> So if you ran ps at exactly the right time (while one of the
> procs on the machine was opening a #-ed file name and
> was between strlen and sprint), you'd win the race.
> You might improve your chances if the machine were
> close to out of memory and the smalloc had to wait for
> more memory.
>
> Oops. Changing those lines to use up->genbuf instead
> of p->genbuf should eliminate the race.
many thanks. i've been chasing this bug for some time. often the
backtrace has been much more confusing.
in fact, ps is run fairly often on this machine because i am
sanguine about dns' stability. if ever there were a canidate for
publish subscribe, it would be dns.
- erik
next reply other threads:[~2008-03-13 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 2:14 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-13 5:57 Brian L. Stuart
2008-03-12 20:08 erik quanstrom
2008-03-13 0:33 ` Russ Cox
2008-03-13 10:44 ` roger peppe
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=b71045ceaf4a0a7dc26c04e459088ad8@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).