From: "Serge E. Hallyn" <serge@hallyn.com>
To: James Morris <jmorris@namei.org>
Cc: "Andrew G. Morgan" <morgan@kernel.org>,
linux-kernel@vger.kernel.org,
Eric Biederman <ebiederm@xmission.com>,
"Serge E . Hallyn" <serge@hallyn.com>
Subject: Re: [PATCH] proc: add SecBits field to /proc/<PID>/status
Date: Fri, 4 Feb 2022 21:10:32 -0600 [thread overview]
Message-ID: <20220205031032.GA14228@mail.hallyn.com> (raw)
In-Reply-To: <d3fc9d9-d99e-a5ab-10a4-7cc60c97e1e@namei.org>
On Fri, Feb 04, 2022 at 04:32:00AM +1100, James Morris wrote:
> On Sun, 30 Jan 2022, Andrew G. Morgan wrote:
>
> > Securebits strongly influence the way Capabilities work for a process,
> > make them visible in the proc status files.
>
> My concern is that this might break some existing userspace code which
> parses the status file.
I don't think anyone should be using that file expecting the fields
in a certain order. No 'grep "^VmRSS:" /proc/self/status' type of
use is going to be broken by this patch. Do you have something else
in mind?
-serge
prev parent reply other threads:[~2022-02-05 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 5:15 [PATCH] proc: add SecBits field to /proc/<PID>/status Andrew G. Morgan
2022-02-03 17:32 ` James Morris
2022-02-04 4:29 ` Andrew G. Morgan
2022-02-05 3:10 ` Serge E. Hallyn [this message]
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=20220205031032.GA14228@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@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