From: "Theodore Ts'o" <tytso@mit.edu>
To: Demi Marie Obenour <demi@invisiblethingslab.com>
Cc: oss-security@lists.openwall.com,
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
Date: Wed, 28 Dec 2022 17:14:42 -0500 [thread overview]
Message-ID: <Y6y/0uzFlTpkw/VT@mit.edu> (raw)
In-Reply-To: <Y6yEv+6iYQQNaqi9@itl-email>
On Wed, Dec 28, 2022 at 01:02:35PM -0500, Demi Marie Obenour wrote:
> > 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’s not add one more thing to the list.
There's always Protobufs[1]! :-) And all of these are better than
ASN.1, for which Google already has a limited parser (for x.509
certificates). :-) :-) :-)
- Ted
next prev parent reply other threads:[~2022-12-28 22:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 16:42 [patch] proc.5: tell how to parse /proc/*/stat correctly Alexey Dobriyan
2022-12-22 22:03 ` [oss-security] " Dominique Martinet
2022-12-22 23:21 ` Solar Designer
2022-12-23 0:15 ` Dominique Martinet
2022-12-23 0:21 ` Jan Engelhardt
2022-12-28 0:44 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-12-28 1:50 ` Tavis Ormandy
2022-12-28 1:50 ` Tavis Ormandy
2022-12-30 20:15 ` Jakub Wilk
2022-12-28 15:24 ` Shawn Webb
2022-12-28 15:31 ` Shawn Webb
2022-12-28 16:47 ` Demi Marie Obenour
2022-12-28 17:09 ` Jan Engelhardt
2022-12-28 17:25 ` Shawn Webb
2022-12-28 18:02 ` Demi Marie Obenour
2022-12-28 18:36 ` John Helmert III
2022-12-28 19:24 ` Shawn Webb
2022-12-28 19:57 ` Alejandro Colomar
2022-12-28 22:14 ` Theodore Ts'o [this message]
2022-12-29 0:33 ` Demi Marie Obenour
2022-12-31 16:31 ` David Laight
2022-12-31 17:27 ` Solar Designer
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=Y6y/0uzFlTpkw/VT@mit.edu \
--to=tytso@mit.edu \
--cc=alx.manpages@gmail.com \
--cc=demi@invisiblethingslab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=oss-security@lists.openwall.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.