Hi! On Wed, 2015-05-27 at 11:42 -0400, Samuel Bronson wrote: > On Wed, May 27, 2015 at 6:12 AM, Zeng Linggang <zenglg.jy@xxxxxxxxxxxxxx> wrote: > > After research, We think fexecve() is thread-safe. But, there > > is not marking of fexecve() in glibc document. > > Um, fexecve() is just like execve(), only on a file descriptor. (In > fact, it appears to be implemented using execve() on > /proc/self/fd/$FD.) > Sorry for the later. Right. After gets the /proc/self/fd/$FD, it begins to using execve(). > As such, the following point from execve(2) applies: > > * All threads other than the calling thread are destroyed during an > execve(). Mutexes, condition variables, and other pthreads objects > are not preserved. > > This does not seem to correspond with the usual notion of "thread > safe", though I guess it would be technically safe to, say, have > several threads racing to run fexecve(). Further text is probably > warranted here. Hmm, the detail information has been list in 'execve'. I think it is not necessary to add further text. Thanks and best regards, Zeng -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
