Ronald Natalie wrote: |vfork() is of use on non-paged (and poorly implemented paging) system\ |s. If you implemented the copy-on-write fork() behavior, you’d not\ | need the vfork KLUDGE. I think there is currently going on some (i haven't really a glue) virtually mapped stack in Linux (thread around [1]), and it seems vfork() there doesn't even copy the page table. So that seems to be a measurable difference. [1] http://www.openwall.com/lists/kernel-hardening/2016/06/21/10 --steffen