Messages in this thread | | | From | (H. Peter Anvin) | Subject | Re: vfork() from userland | Date | 1 Feb 1999 21:49:20 GMT |
| |
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/
| |