From: Daniel Reichelt <debian@nachtgeist.net>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: procfs: boot- and runtime configurable access mode for /proc/<pid> dirs
Date: Thu, 24 Mar 2011 09:41:58 +0100 [thread overview]
Message-ID: <4D8B03D6.2090204@nachtgeist.net> (raw)
In-Reply-To: <20110324073225.GA3806@p183.telecom.by>
> Keeping u/g/o inside kernel is horrible.
Why exactly? Since it's only a char and not char[] I don't see the
disadvantage over int or a define or whatever. Of course I could always
change that if that's a de-facto standard I just didn't know about.
> What is the usecase? Content of /proc/* is identical.
Use-case is to isolate process information from other users' or groups'
eyes, e.g. with 550 the output of ps aux only lists processes of the
groups your user is a member of.
next prev parent reply other threads:[~2011-03-24 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 4:09 procfs: boot- and runtime configurable access mode for /proc/<pid> dirs Daniel Reichelt
2011-03-24 7:32 ` Alexey Dobriyan
2011-03-24 8:41 ` Daniel Reichelt [this message]
2011-03-24 18:22 ` Alexey Dobriyan
2011-03-24 18:44 ` Al Viro
2011-03-24 18:49 ` Daniel Reichelt
2011-03-24 19:18 ` Daniel Reichelt
2011-03-24 20:37 ` Al Viro
2011-03-25 21:24 ` Christian Kujau
2011-05-26 10:56 ` Al Viro
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=4D8B03D6.2090204@nachtgeist.net \
--to=debian@nachtgeist.net \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@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