[PATCH 2/3] posix: Improve default posix_spawn implementation

[Adhemerval Zanella]

On 03/07/2017 10:02, Andreas Schwab wrote:
> On Jul 03 2017, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
> 
>> My understanding is POSIX is not strictly regarding spurious errno writes,
>> but on general information [1] it has the rationale:
>>
>> "In order to avoid this problem altogether for new functions, these 
>> functions avoid using errno and, instead, return the error number directly 
>> as the function return value; a return value of zero indicates that no 
>> error was detected."
> 
> It also notes (in section Signal Actions):
> 
> "Note in particular that even the "safe'' functions may modify the global
> variable errno"

So it is more an implementation detail and/or QoI to whether modify errno
on such functions and see no impeding reason of doing it on posix_spawn.
The only rationale I am not sure is if its worth to remove clone wrapper
error path setting errno.