LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

readv.2, pipe.7: Make text on pipe writes more general to avoid a confusion in writev(2) 

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: наб <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2021-08-08 11:24:16 +02:00
parent bd62f2240b
commit 9b94b63df5
2 changed files with 2 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
man2/readv.2
View File

@ -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,

4
man7/pipe.7
View File

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