When a process first issues setuid() and then goes on to create threads,
those threads run under the setuid() uid - all is well.
However, once the first thread is created, only the thread calling setuid()
gets setuid in fact. All new threads continue to be created as root.
This behaviour exists under 2.2.18 with glibc 2.1.3 and under 2.4.17 with
glibc 2.2.5, and is shown using the brief program attached.
Is this by design? It appears that all threads created get the uid of the
thread manager process.
>From our standpoint as an application developer, this is nasty. It means
that we have to do everything that needs root before creating the first
thread. This behaviour is also highly non obvious.
A fix would appear to need a 'clone with uid' syscall, other solutions will
probably cause race condition.
Regards,
bert
-- http://www.PowerDNS.com Versatile DNS Software & Services http://www.tk the dot in .tk Netherlabs BV / Rent-a-Nerd.nl - Nerd Available - Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:01:02 EST