Remove Context::vfork.
Since clone is no longer exists as a syscall, it makes little sense to manage vfork in the kernel. Implementing vfork in userspace would still be possible.
Loading
Please register or sign in to comment
Since clone is no longer exists as a syscall, it makes little sense to manage vfork in the kernel. Implementing vfork in userspace would still be possible.