[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] pipe2: document lack of thread-safety in replacement

From: Bruno Haible
Subject: Re: [PATCH] pipe2: document lack of thread-safety in replacement
Date: Thu, 26 Jan 2012 15:28:17 +0100
User-agent: KMail/4.7.4 (Linux/3.1.0-1.2-desktop; KDE/4.7.4; x86_64; ; )

Eric Wong wrote:
> As the replacement cannot be made thread-safe, we need to
> document this to prevent users from having a false sense
> of safety.
> * doc/glibc-functions/pipe2.texi (pipe2): mention lack of thread-safety

Can you please describe a situation with multiple threads where gnulib's
pipe2() implementation would lead to problems?

>  I took the line off the existing documentation for the
>  similar-in-purpose *at() functions.

The other functions (openat, renameat, etc.) are marked "not multithread-
safe" because they depend on the 'save-cwd' module. But 'pipe2' doesn't.
So what's the MT problem you are seeing with lib/pipe2.c?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]