Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: iac594737:Fastmail
Date:   Wed, 28 Dec 2022 13:02:35 -0500
From:   Demi Marie Obenour <demi@invisiblethingslab.com>
To:     oss-security@lists.openwall.com
Cc:     Alejandro Colomar <alx.manpages@gmail.com>,
        Michael Kerrisk <mtk.manpages@gmail.com>,
        linux-kernel@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [oss-security] [patch] proc.5: tell how to parse /proc/*/stat
 correctly
Message-ID: <Y6yEv+6iYQQNaqi9@itl-email>
References: <Y6SJDbKBk471KE4k@p183>
 <Y6TUJcr/IHrsTE0W@codewreck.org>
 <1a1963aa1036ba07@orthanc.ca>
 <20221228152458.6xyksrxunukjrtzx@mutt-hbsd>
 <Y6xzIR9P+a6uaaEx@itl-email>
 <20221228172517.l7h3m7wjfpxr3dzw@mutt-hbsd>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="h7PZ10vsTAyj4PIA"
Content-Disposition: inline
In-Reply-To: <20221228172517.l7h3m7wjfpxr3dzw@mutt-hbsd>
Precedence: bulk


--h7PZ10vsTAyj4PIA
Content-Type: text/plain; protected-headers=v1; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Date: Wed, 28 Dec 2022 13:02:35 -0500
From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: oss-security@lists.openwall.com
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-kernel@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [oss-security] [patch] proc.5: tell how to parse /proc/*/stat
 correctly

On Wed, Dec 28, 2022 at 12:25:17PM -0500, Shawn Webb wrote:
> On Wed, Dec 28, 2022 at 11:47:25AM -0500, Demi Marie Obenour wrote:
> > On Wed, Dec 28, 2022 at 10:24:58AM -0500, Shawn Webb wrote:
> > > On Tue, Dec 27, 2022 at 04:44:49PM -0800, Lyndon Nerenberg (VE7TFX/VE=
6BBM) wrote:
> > > > Dominique Martinet writes:
> > > >=20
> > > > > But, really, I just don't see how this can practically be said to=
 be parsable...
> > > >=20
> > > > In its current form it never will be.  The solution is to place
> > > > this variable-length field last.  Then you can "cut -d ' ' -f 51-"
> > > > to get the command+args part (assuming I counted all those fields
> > > > correctly ...)
> > > >=20
> > > > Of course, this breaks backwards compatability.
> > >=20
> > > It would also break forwards compatibility in the case new fields
> > > needed to be added.
> > >=20
> > > The only solution would be a libxo-style feature wherein a
> > > machine-parseable format is exposed by virtue of a file extension.
> > >=20
> > > Examples:
> > >=20
> > > 1. /proc/pid/stats.json
> > > 2. /proc/pid/stats.xml
> > > 3. /proc/pid/stats.yaml_shouldnt_be_a_thing
> >=20
> > A binary format would be even better.  No risk of ambiguity.
>=20
> I think the argument I'm trying to make is to be flexible in
> implementation, allowing for future needs and wants--that is "future
> proofing".

Linux should not have an XML, JSON, or YAML serializer.  Linux already
does way too much; let=E2=80=99s not add one more thing to the list.
--=20
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab

--h7PZ10vsTAyj4PIA
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmOshMAACgkQsoi1X/+c
IsFRcRAAyi/536j5gBlVkcg6xT9EIcHZq2MRXB1xoJuKa5bRWIH6vBDgH924yy7i
gSNF0CfemdwbPvI/SCF5E+MdJJPzYlb1cyZe8faDey92XGKadi7w61YQSZT/sLT5
Oa66GmF+BcPi5v7wPArP8dOXHItwG7nazKZehsWcWk6pX2TBW6xvVBgmjQlDXNFM
KdgeSKnD6nBr3ehkr1u3U8FdTCoy1x7+3M7aZDQsho23gJ2EGLZP4tEMrJuhU6ny
gMCM0GVvLJhEbw7cpV+2qCDs9nGEIuma99RXHYQq5gzjIQD7X+FbWpa75KigpS7a
nDB/ZdY8DJ4sychM1/GqSqckrOoazq8kTQHrF3BbOHFZ5NUMiPK9BPO18x76DfuY
L/gzOxeZmmu0bq0WUBJQg/vlmvAINZTw3C6j9q5P9HPOb1DbiMVJbk0XJ6GplSNL
W7BN6bHHsKa05QGXzF7j6Kk2BBnyzXDKzIgkexP+pDR5ZTyKkijQGxIOdTV5qO4R
DfcpQAGX5x2R2kxD8jtMt1d+Nky1/lziX0n9+nXo0OO6uevjDrj0aPY+01N9OGM2
rqqscUS9mUuT8v/5+1CkNhl0G009b673iKyZVN9QM7MhGMypwQJ6IMS8hRgFcqjl
XFanvw16iKAKxSRt2s1bckswJ/TlXNsGwjvAJreboDybPHBpewY=
=Wdo0
-----END PGP SIGNATURE-----

--h7PZ10vsTAyj4PIA--