https://bugzilla.kernel.org/show_bug.cgi?id=215769 --- Comment #3 from Коренберг Марк (socketpair@xxxxxxxxx) --- Hi, I appreciate depth of information validation. Actually, you are right. vfork() DOES work with pid=1 processes. I figured out the cause in my case. In order to reproduce -- add unshare(CLONE_NEWTIME) just before vfork(). Now, I don't know if it's a bug in vfork() or in fork(). Yes, both are clone() actually. In any case, they should either both give EINVAL or both don't fail. But it's definitely bug in the kernel around CLONE_NEWTIME. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
