From: Stuart Anderson <anderson@netsweng.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] clone syscall fix
Date: Sat, 31 Mar 2007 21:52:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703312147020.5290@trantor.stuart.netsweng.com> (raw)
In-Reply-To: <20070331192104.GC24690@networkno.de>
On Sat, 31 Mar 2007, Thiemo Seufer wrote:
> Stuart Anderson wrote:
>>
>> Even though clone() and fork() are related, they don't seem to be close
>> enough to allow a single routine to be used to implement both. With this
>> patch, the LTP tests for clone now pass.
>
> But it still does the same, assuming VM_CLONE is set, except for passing
> additional arguments to the host call.
I'm not so sure that the VM_CLONE flag should control wether the new
stack is set up or not. There are tests for newsp == NULL inside that
block anyway. The LTP certainly tests combination for which the
do_fork() code doesn't work.
> Passing untranslated regs looks
> like a bug to me, I'm unsure about the tls_val.
Hmm, could be, but that's the way it is in the current code. I think
more testing on additional combination sof target &host will be needed.
>> It may be possible to fold this back into do_fork(), but this just seemed to
>> be a little bit more straightforward.
>
> Since Linux's fork() is just a specialcase of clone() this should be
> done eventually.
I'll try just dropping do_fork completely, and see if this new do_clone()
works for the fork case also. If so, then that effectively folds the
changes back into do_fork(), and more closely resembles that non-emulated
case of fork() being implemnted on top of clone( anyway.
Stuart
Stuart R. Anderson anderson@netsweng.com
Network & Software Engineering http://www.netsweng.com/
1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
BD03 0A62 E534 37A7 9149
prev parent reply other threads:[~2007-04-01 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 1:45 [Qemu-devel] [PATCH] clone syscall fix Stuart Anderson
2007-03-31 19:21 ` Thiemo Seufer
2007-04-01 1:52 ` Stuart Anderson [this message]
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.LNX.4.64.0703312147020.5290@trantor.stuart.netsweng.com \
--to=anderson@netsweng.com \
--cc=qemu-devel@nongnu.org \
--cc=ths@networkno.de \
/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).