Re: [PATCH v2 1/4] posix_spawn.3: Document implementation using clone() since glibc 2.24

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Florian,

On 10/20/18 11:35 AM, Florian Weimer wrote:
> * Olivier Gayot:
> 
>> As a consequence, the statements regarding the use of the flag
>> POSIX_SPAWN_USEVFORK and how the function decides whether it should use
>> fork (2) or vfork (2) are obsolete since glibc 2.24.
> 
> Maybe we should add that it is always never correct to use
> POSIX_SPAWN_USEVFORK?
> 
> Either you are on a glibc which ignores it, then it is pointless, or
> on a glibc which has buggy semantics when vfork is used, so you
> probably do not want to use it.

Could you formulate a sentence for me that I could drop into
the current manual page?

Are there any bug reports about the older buggy semantics that I
can add as part of a commit message?

Thanks,

Michael



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux