]> git.ipfire.org Git - thirdparty/man-pages.git/commitdiff
proc_pid_io.5: Mention atomicity in atomicity note
authorнаб <nabijaczleweli@nabijaczleweli.xyz>
Wed, 13 Mar 2024 14:26:50 +0000 (15:26 +0100)
committerAlejandro Colomar <alx@kernel.org>
Thu, 14 Mar 2024 16:28:03 +0000 (17:28 +0100)
And drop "current implementation"
(wording still literal from Documentation/filesystems/proc.rst).
Of course this describes the current implementation.

Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
man5/proc_pid_io.5

index 1948fff1801b57aed3e39148c949f189505a1987..58fd9a5ab09dd903935c420bb0bd08eb6da44625 100644 (file)
@@ -84,11 +84,10 @@ will not be happening.
 .RE
 .IP
 .IR Note :
-In the current implementation, things are a bit racy on 32-bit systems:
-if process A reads process B's
-.IR /proc/ pid /io
-while process B is updating one of these 64-bit counters,
-process A could see an intermediate result.
+these counters are not atomic:
+on systems where 64-bit integer operations may tear,
+a counter could be updated simultaneously with a read,
+yielding an incorrect intermediate value.
 .IP
 Permission to access this file is governed by
 .BR ptrace (2)