From: Riku Voipio <riku.voipio@iki.fi>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: implement pipe2 syscall
Date: Wed, 6 May 2009 17:26:05 +0300 [thread overview]
Message-ID: <20090506142605.GA27875@kos.to> (raw)
In-Reply-To: <200905061323.29083.paul@codesourcery.com>
On Wed, May 06, 2009 at 01:23:28PM +0100, Paul Brook wrote:
> On Wednesday 06 May 2009, Riku Voipio wrote:
> > On Wed, May 06, 2009 at 12:08:32PM +0100, Jamie Lokier wrote:
> > > But it's not a bug to call execve(), or fork() then execve(), in
> > > another thread at the same time as descriptors are being created.
> > > Those calls scan the whole file descriptor table, and look at the
> > > FD_CLOEXEC flags.
> >
> > Now this discussion would be much more useful if qemu was actually
> > properly threadsafe to begin with...
> For usermode emulation it is.
Ok, I was under impression that threads in qemu linux-user were still
considered broken.
I'll see what would be the best way handle the CLOEXEC flags in a safe
manner.
next prev parent reply other threads:[~2009-05-06 14:26 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
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 [this message]
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=20090506142605.GA27875@kos.to \
--to=riku.voipio@iki.fi \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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).