9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Potential race in syspipe()
Date: Tue, 15 Aug 2000 15:42:00 -0400	[thread overview]
Message-ID: <200008151942.PAA04608@augusta.math.psu.edu> (raw)
In-Reply-To: <Pine.GSO.4.10.10008132154210.194-100000@weyl.math.psu.edu>

In article <Pine.GSO.4.10.10008132154210.194-100000@weyl.math.psu.edu> you write:
>	I realize very well that changing that would be painful - the best
>strategy is probably to ask for space at the very beginning and keep the
>number of pending allocations (i.e. make sure that newfd() never fails).
>Yuck. I'll probably try to see what this approach gives on our side, but
>I'm not sure that it will be any better than our current code (right now
>we are using an equivalent of falloc(9); since we keep a bitmap of
>allocated descriptors we can see if dup2() tries to stick its nose into
>the pending slot). newfd() equivalent had been tried some time ago, but
>back then it was rejected due to problems with creat(2).
>	At least you don't have to deal with bloody SCM_RIGHTS
>file-passing...

So why is RedHat interested in Plan 9?  :-)

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.  Unix sucks
now days anyway (damn, I'm starting to sound like Oleg....)

	- Dan C.



  reply	other threads:[~2000-08-15 19:42 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 [this message]
2000-08-16 11:58     ` Alexander Viro
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=200008151942.PAA04608@augusta.math.psu.edu \
    --to=cross@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).