From: Jamie Lokier <jamie@shareable.org>
To: Martin Mohring <martin.mohring@opensuse.org>
Cc: Riku Voipio <riku.voipio@iki.fi>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: implement pipe2 syscall
Date: Wed, 6 May 2009 11:53:37 +0100 [thread overview]
Message-ID: <20090506105337.GB23364@shareable.org> (raw)
In-Reply-To: <4A0155F6.9000801@opensuse.org>
Martin Mohring wrote:
> >> The point of pipe2() with FD_CLOEXEC is to be atomic: make sure
> >> another thread can never see the file descriptor with FD_CLOEXEC not set.
> >
> How do we want to handle if "O_CLOEXEC" is not defined on the host OS,
> because kernel too old (Debian Etch, CentOS 5)? Should it then return
> ENOSYS?
You can emulate it on any host OS using a mutex or read-write lock:
- Acquire the lock for reading before calling the hosts's
open/pipe/socket/etc.
- Release the lock after calling the host's fcntl to set FD_CLOEXEC.
- Acquire the lock for writing around emulation of fork, exec,
clone and unshare.
There are ways to do it more efficiently without a lock, but I don't
think they are worth bothering with here.
-- Jamie
next prev parent reply other threads:[~2009-05-06 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 13:30 [Qemu-devel] [PATCH] linux-user: implement pipe2 syscall Riku Voipio
2009-05-05 20:43 ` [Qemu-devel] [PATCH] linux-user: implement pipe2 syscall [v2] Riku Voipio
2009-05-05 22:58 ` [Qemu-devel] [PATCH] linux-user: implement pipe2 syscall Jamie Lokier
2009-05-06 8:00 ` Riku Voipio
2009-05-06 9:18 ` Martin Mohring
2009-05-06 10:53 ` Jamie Lokier [this message]
2009-05-06 11:02 ` Riku Voipio
2009-05-06 11:08 ` Jamie Lokier
2009-05-06 12:02 ` Riku Voipio
2009-05-06 12:23 ` Paul Brook
2009-05-06 14:26 ` Riku Voipio
2009-05-06 12:46 ` Martin Mohring
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=20090506105337.GB23364@shareable.org \
--to=jamie@shareable.org \
--cc=martin.mohring@opensuse.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.