Re: [PATCH 01/23] pipe.7: also mention writev(2) in atomicity section
From: Alejandro Colomar (man-pages) <hidden>
Date: 2021-08-08 13:20:36
Hi Michael, On 8/8/21 10:41 AM, Alejandro Colomar wrote:
From: наб <redacted> writev(2) notes that buffers don't interleave with other process' (a reasonable question to ask), but points to pipe(7) for an exception. pipe(7) did /not/ mention "writev", "iov", "scat", or "gath", which are, in order, reasonable search terms: this was confusing at best and alarming at worst By mentioning writev(2) in the heading, we clearly note that this sort of interleaving behaviour matches write(2)'s and isn't a concern Signed-off-by: Ahelenia Ziemiańska <redacted> Signed-off-by: Alejandro Colomar <redacted>
Oops, drop this one that I already sent in the previous set. Cheers, Alex
quoted hunk ↗ jump to hunk
--- man7/pipe.7 | 2 ++ 1 file changed, 2 insertions(+)diff --git a/man7/pipe.7 b/man7/pipe.7 index c3210320c..29f6cf6cb 100644 --- a/man7/pipe.7 +++ b/man7/pipe.7@@ -246,6 +246,8 @@ limits; see BUGS. .SS PIPE_BUF POSIX.1 says that .BR write (2)s +and +.BR writev (2)s of less than .B PIPE_BUF bytes must be atomic: the output data is written to the pipe as a
-- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/