From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 4/6] proc_pid_io.5: mention atomicity in atomicity note
Date: Thu, 14 Mar 2024 17:28:31 +0100 [thread overview]
Message-ID: <ZfMlsHDbBT-sswDb@debian> (raw)
In-Reply-To: <bf3b3c49fca51b0fbfb85fc905bfc9030f106d1c.1710339990.git.nabijaczleweli@nabijaczleweli.xyz>
[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]
Hi,
> Subject: Re: [PATCH 4/6] proc_pid_io.5: mention atomicity in atomicity note
Please use uppercase after the prefix. That is:
proc_pid_io.5: Mention atomicity in atomicity note
At least to me, it seems to help see where the sentence starts. Maybe
you can convince me of the opposite, though, if you try.
On Wed, Mar 13, 2024 at 03:26:50PM +0100, наб wrote:
> 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>
> ---
> man5/proc_pid_io.5 | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/man5/proc_pid_io.5 b/man5/proc_pid_io.5
> index 4d97bd95f..181717192 100644
> --- a/man5/proc_pid_io.5
> +++ b/man5/proc_pid_io.5
> @@ -82,11 +82,10 @@ .SH DESCRIPTION
> .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.
Hmmm, I think this should be a CAVEATS section. Since you'll have to
send more patches for this page, would you mind adding one that moves
this paragraph to a CAVEATS section?
Anyway, I've applied this patch. Thanks!
Cheers,
Alex
> .IP
> Permission to access this file is governed by
> .BR ptrace (2)
> --
> 2.39.2
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-14 16:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 14:26 [PATCH 1/6] proc_pid_io.5: stats include children наб
2024-03-13 14:26 ` [PATCH 2/6] proc_pid_io.5: dewafflify наб
2024-03-14 16:21 ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 3/6] proc_pid_io.5: wfix наб
2024-03-14 16:22 ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 4/6] proc_pid_io.5: mention atomicity in atomicity note наб
2024-03-14 16:28 ` Alejandro Colomar [this message]
2024-03-13 14:26 ` [PATCH 5/6] getrusage.2: proc(5) /proc/pid/stat -> proc_pid_stat(5) наб
2024-03-14 16:31 ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 6/6] getrusage.2, proc_pid_io.5: crosslink наб
2024-03-14 16:33 ` Alejandro Colomar
2024-03-14 16:19 ` [PATCH 1/6] proc_pid_io.5: stats include children Alejandro Colomar
2024-03-17 11:01 ` [PATCH v2 2/2] proc_pid_io.5: dewafflify наб
2024-03-17 12:15 ` Alejandro Colomar
2024-03-17 13:31 ` [PATCH v3] " наб
2024-03-17 14:12 ` Alejandro Colomar
2024-03-17 15:37 ` [PATCH v4] " наб
2024-03-17 16:08 ` Alejandro Colomar
2024-03-17 11:01 ` [PATCH v2 1/2] proc_pid_io.5: stats include children наб
2024-03-17 11:39 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZfMlsHDbBT-sswDb@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox