From: Thorsten Glaser <tg@mirbsd.de>
To: Donald Buczek <buczek@molgen.mpg.de>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
linux-fsdevel@vger.kernel.org, 1024811@bugs.debian.org
Subject: Re: Bug#1024811: linux: /proc/[pid]/stat unparsable
Date: Fri, 23 Dec 2022 08:49:31 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.2212230847310.9463@herc.mirbsd.org> (raw)
In-Reply-To: <b3ed92e0-6135-7f0c-6b6b-1be9dfe7a8a1@molgen.mpg.de>
Donald Buczek dixit:
> To be fair, this daemon doesn't use /proc/pid/stat for that, but /proc/pid/comm
Yes, and that’s proper. The field in /proc/pid/stat is size-limited
and so not necessarily distinct.
> As /proc/pid/stat is also used in many places, it could as well use
> that to avoid code duplication or reuse data already read from the
> other source.
No, because the data in /stat is incomplete *and* anything using
it that would be affected by escaping was already broken.
bye,
//mirabilos
--
22:20⎜<asarch> The crazy that persists in his craziness becomes a master
22:21⎜<asarch> And the distance between the craziness and geniality is
only measured by the success 18:35⎜<asarch> "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent
next prev parent reply other threads:[~2022-12-23 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166939644927.12906.17757536147994071219.reportbug@x61w.mirbsd.org>
2022-11-25 17:24 ` Bug#1024811: linux: /proc/[pid]/stat unparsable Thorsten Glaser
[not found] ` <Y4Hshbyk9TEsSQsm@p183>
2022-12-22 0:53 ` Thorsten Glaser
2022-12-22 13:45 ` Donald Buczek
2022-12-22 20:28 ` Thorsten Glaser
2022-12-23 8:42 ` Donald Buczek
2022-12-23 8:49 ` Thorsten Glaser [this message]
2022-12-23 9:11 ` Donald Buczek
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=Pine.BSM.4.64L.2212230847310.9463@herc.mirbsd.org \
--to=tg@mirbsd.de \
--cc=1024811@bugs.debian.org \
--cc=adobriyan@gmail.com \
--cc=buczek@molgen.mpg.de \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).