[Bug nptl/13347] Threaded setuid() can wrongly report success when failing to drop privileges

[bugdal at aerifal dot cx]

https://sourceware.org/bugzilla/show_bug.cgi?id=13347

--- Comment #14 from Rich Felker <bugdal at aerifal dot cx> ---
I've seen real-world applications that were _potentially_ affected. In
particular, Java applications which call setuid at startup (e.g. after binding
to a port) have often (possibly inadvertently) created threads before doing so.
It may be very unlikely for setuid to fail in some of the threads at system
startup, but if restarting a server that aborted due to some sort of resource
exhaustion, it might be a lot more likely. I never attempted to observe the
issue actually happening in such apps, however; I just noted that it could.

-- 
You are receiving this mail because:
You are on the CC list for the bug.