Hi,

On Fri, 2015-06-12 at 21:01 +0200, Michael Kerrisk (man-pages) wrote:

Hi Zeng Linggang,

On 05/27/2015 05:42 PM, Samuel Bronson wrote:

quoted

On Wed, May 27, 2015 at 6:12 AM, Zeng Linggang [off-list ref] wrote:

quoted

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.)

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.

Did you have any thoughts on Samuel's point?

Thanks for your remind, I almost miss it.

As we can see, the detail information has been list in 'execve'. I think
it is not necessary to add further text.

Best regards,
Zeng

Cheers,

Michael

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html