diff options
| author | наб <nabijaczleweli@nabijaczleweli.xyz> | 2024-03-13 15:26:50 +0100 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2024-03-14 17:28:03 +0100 |
| commit | d4d342fdcd5274900ac5f1ecc2ff5acacec2bb5f (patch) | |
| tree | 6ac7f59d22e056ed62dce9dc3a92bb781d63b40c | |
| parent | 524010ffc81adddcabda5613acc5b5024b176ba2 (diff) | |
proc_pid_io.5: Mention atomicity in atomicity note
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>
| -rw-r--r-- | man5/proc_pid_io.5 | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/man5/proc_pid_io.5 b/man5/proc_pid_io.5 index 1948fff18..58fd9a5ab 100644 --- a/man5/proc_pid_io.5 +++ b/man5/proc_pid_io.5 @@ -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) |