From: Alexander Viro <viro@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Potential race in syspipe()
Date: Wed, 16 Aug 2000 07:58:07 -0400 [thread overview]
Message-ID: <Pine.GSO.4.10.10008160159140.194-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <200008151942.PAA04608@augusta.math.psu.edu>
On Tue, 15 Aug 2000, Dan Cross wrote:
> So why is RedHat interested in Plan 9? :-)
Redhat is interested? I didn't know that...
> btw- BSD has had rfork() since at least '96, if not longer. It
> was just never used. Scott Schwartz and I were at one point going
> to look into make it more robust, but never bothered.
Ugh... I've looked at the *BSD side. FreeBSD-CURRENT handling of shared
descriptor tables is choke-full of panicable races. OpenBSD is more or
less free of the obvious ones, but they still have open()/dup2() races.
FreeBSD is roughly at the stage we were in Spring '99 before the large
VFS threading - I had to go through the upper layers anyway, so cleaning
them up and closing the races was an obvious idea. Several races survived
- the last group had been hunted down and shot quite recently (sitting
down to write description gave usual results). OpenBSD is somewhat between
FreeBSD and Linux in that respect. I didn't do the full analysis of Plan 9
handling of the same area, but the quick check showed only a dubious place
in syspipe() - everything else seems to be fine. Constructing a race once
you know what place needs attention... <shrug> SOP.
> Unix sucks
> now days anyway (damn, I'm starting to sound like Oleg....)
psu.flame is ---> that way. Umm... Maybe a good idea - place seems to be
quite dead lately...
next prev parent reply other threads:[~2000-08-16 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-14 1:47 presotto
2000-08-14 2:42 ` Alexander Viro
2000-08-15 19:42 ` Dan Cross
2000-08-16 11:58 ` Alexander Viro [this message]
2000-08-16 12:36 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2000-08-14 4:30 presotto
2000-08-14 4:50 ` Alexander Viro
2000-08-11 11:20 Alexander Viro
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=Pine.GSO.4.10.10008160159140.194-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--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).