public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>,
	Tejun Heo <tj@kernel.org>, Craig Small <csmall@enc.com.au>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH 0/2] proc.5: note broken v4.18 userspace promise
Date: Wed, 28 Dec 2022 21:26:21 +0100	[thread overview]
Message-ID: <cf8e5404-f3bc-8a27-9cd0-2cdc0c26d030@gmail.com> (raw)
In-Reply-To: <CAHk-=wh6f8+e7Nm1nj1yNGB7d1SivgrBw8Gd3Ow58pc+NoNi1w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1886 bytes --]

Hi,

On 12/23/22 19:12, Linus Torvalds wrote:
> On Fri, Dec 23, 2022 at 10:00 AM Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>>
>> Whereas the fix here is a fix for a promise we're currently making
>> which hasn't been true since v4.18.
> 
> Hah. Ack. Did anybody ever actually notice?
> 
> I wonder if the newer limit of 64 characters for kworkers shouldn't
> even be mentioned at all, and if the 16-byte truncation for user space
> should also be just removed.
> 
> Those limits should never have been some documented API, they were
> always just implementation details, after all.
> 
>               Linus


I agree.  A variable implementation detail like this doesn't provide anything 
valuable to users; especially since there's no statbility promise at all.  I'd 
rewrite to just remove the (16) implementation detail.

Ævar, would you send an v2 that removes implementation details, rather than 
fixing the details?

Thanks for the patch set!

Cheers,

Alex

On 12/23/22 18:59, Ævar Arnfjörð Bjarmason wrote:
 > diff --git a/man5/proc.5 b/man5/proc.5
 > index 115c8592e..b23dd1479 100644
 > --- a/man5/proc.5
 > +++ b/man5/proc.5
 > @@ -2092,9 +2092,13 @@ The filename of the executable, in parentheses. Tools 
such as
 >   may alternatively (or additionally) use
 >   .IR/proc/  pid /cmdline.
 >   .IP
 > -Strings longer than
 > +For userspace, strings longer than
 >   .B TASK_COMM_LEN
 >   (16) characters (including the terminating null byte) are silently truncated.
 > +Since Linux version 4.18.0 a longer limit of 64 (including the
 > +terminating null byte) has applied to the kernel's own workqueue
 > +workers (whose names start with "kworker/").
 > +.IP
 >   This is visible whether or not the executable is swapped out.
 >   .TP
 >   (3) \fIstate\fP \ %c

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-28 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23 17:59 [PATCH 0/2] proc.5: note broken v4.18 userspace promise Ævar Arnfjörð Bjarmason
2022-12-23 17:59 ` [PATCH 1/2] proc.5: note that "cmdline" might be favored over "stat.comm" by ps(1) Ævar Arnfjörð Bjarmason
2022-12-28 20:27   ` Alejandro Colomar
2022-12-23 17:59 ` [PATCH 2/2] proc.5: the "comm" field can be longer than 16 bytes Ævar Arnfjörð Bjarmason
2022-12-23 18:12 ` [PATCH 0/2] proc.5: note broken v4.18 userspace promise Linus Torvalds
2022-12-28 20:26   ` Alejandro Colomar [this message]
2023-01-04 20:59     ` Ævar Arnfjörð Bjarmason
2023-01-04 17:19   ` Tejun Heo

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=cf8e5404-f3bc-8a27-9cd0-2cdc0c26d030@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=alx@kernel.org \
    --cc=avarab@gmail.com \
    --cc=csmall@enc.com.au \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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