From 9b94b63df56421eb8f207a07e8aa462e2fe4e3d6 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Sun, 8 Aug 2021 11:24:16 +0200 Subject: [PATCH] readv.2, pipe.7: Make text on pipe writes more general to avoid a confusion in writev(2) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After a patch proposal from наб triggered by concerns that, when talking about PIPE_BUF, pipe(7) explicitly mentions write(2) but not writev(2), I've concluded that the reference in writev(2) to pipe(7) is not needed (mea culpa; I added that text), and I think the text in pipe(7) could be written to be closer to the POSIX spec, which doesn't talk about "write() calls", but simply about "writes". Reported-by: наб Signed-off-by: Michael Kerrisk --- man2/readv.2 | 4 +--- man7/pipe.7 | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/man2/readv.2 b/man2/readv.2 index bd0a6cd2f..c066c73a5 100644 --- a/man2/readv.2 +++ b/man2/readv.2 @@ -141,9 +141,7 @@ are atomic: the data written by .\" Regarding atomicity, see https://bugzilla.kernel.org/show_bug.cgi?id=10596 .BR writev () is written as a single block that is not intermingled with output -from writes in other processes (but see -.BR pipe (7) -for an exception); +from writes in other processes; analogously, .BR readv () is guaranteed to read a contiguous block of data from the file, diff --git a/man7/pipe.7 b/man7/pipe.7 index c3210320c..d79768fb6 100644 --- a/man7/pipe.7 +++ b/man7/pipe.7 @@ -244,9 +244,7 @@ and limits; see BUGS. .\" .SS PIPE_BUF -POSIX.1 says that -.BR write (2)s -of less than +POSIX.1 says that writes of less than .B PIPE_BUF bytes must be atomic: the output data is written to the pipe as a contiguous sequence.