lkml.org 
[lkml]   [1999]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: vfork() from userland
Date
Followup to:  <19990201131820.A8292@draper.net>
By author: kernel@draper.net
In newsgroup: linux.dev.kernel
>
> I have been been playing with the new vfork syscall... it seems that
> the child when embarking down the execve syscall road murders its parent.
> No doubt I will appear foolish before the world (Linus, may I borrow the
> brown paper bag please).
>
> My gut says the solution lies in protecting the parent's stack... but,
> I have yet to figure out the bloody thing.
>

No, the solution lies in the fact that vfork() *must* be an inline
(not using the stack.) As far as I know, syscall() isn't, although
syscallN() is.

-hpa
--
"Linux is a very complete and sophisticated operating system. There
are, and will be, large numbers of applications available for it."
-- Paul Maritz, Group Vice President for Platforms And Applications,
Microsoft Corporation [Reference at: http://www.kernel.org/~hpa/ms.html]

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.038 / U:0.232 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site