From: Giacomo Tesio <giacomo@tesio.it>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] create/create race
Date: Tue, 24 May 2016 23:25:47 +0200 [thread overview]
Message-ID: <CAHL7psE__LHoBmm9rFwJV94wU64TYYUMywqkR9LP6VQdNWVQOg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
I'm pretty curious about the create(2)/create(5) race described in a
comment in namec (see
https://github.com/brho/plan9/blob/master/sys/src/9/port/chan.c#L1564-L1603)
Does anyone know or remember the reasoning behind this design?
What was wrong about using the create(5) semantics for the create(2)
syscall?
Giacomo
[-- Attachment #2: Type: text/html, Size: 495 bytes --]
next reply other threads:[~2016-05-24 21:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 21:25 Giacomo Tesio [this message]
2016-11-30 11:04 ` Giacomo Tesio
2016-11-30 11:19 ` cinap_lenrek
2016-11-30 13:14 ` G. David Butler
2016-11-30 13:32 ` cinap_lenrek
2016-11-30 13:53 ` Charles Forsyth
2016-11-30 15:02 ` Giacomo Tesio
2016-11-30 15:08 ` Charles Forsyth
2016-11-30 15:28 ` Giacomo Tesio
2016-11-30 15:34 ` Charles Forsyth
2016-11-30 15:40 ` cinap_lenrek
2016-11-30 16:16 ` Giacomo Tesio
2016-11-30 21:51 ` Charles Forsyth
2016-11-30 21:53 ` Charles Forsyth
2016-11-30 23:15 ` Giacomo Tesio
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=CAHL7psE__LHoBmm9rFwJV94wU64TYYUMywqkR9LP6VQdNWVQOg@mail.gmail.com \
--to=giacomo@tesio.it \
--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).