From: Kees Cook <kees.cook@canonical.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: add "personality" to process status file
Date: Sun, 5 Oct 2008 03:07:01 -0700 [thread overview]
Message-ID: <20081005100701.GQ10632@outflux.net> (raw)
In-Reply-To: <20081005091120.GA21003@x200.localdomain>
On Sun, Oct 05, 2008 at 01:11:20PM +0400, Alexey Dobriyan wrote:
> On Sat, Oct 04, 2008 at 05:48:43PM -0700, Arjan van de Ven wrote:
> > On Sat, 4 Oct 2008 17:42:33 -0700
> > Kees Cook <kees.cook@canonical.com> wrote:
> >
> > > On Sat, Oct 04, 2008 at 04:42:39PM -0700, Arjan van de Ven wrote:
> > > > On Sat, 4 Oct 2008 15:02:20 -0700
> > > > Kees Cook <kees.cook@canonical.com> wrote:
> > > > > Nothing else seemed appropriate, but I could make a brand new proc
> > > > > file, if that's sensible. "status_private" ?
> > > >
> > > > how about a file called "personality" that has each set bit as an
> > > > ascii version ?
> > > > (one per line maybe)
> > >
> > > Well, it's a one-to-many due to how the personality types are defined,
> > > so doing a bitfield-to-ASCII-names conversion wouldn't really work
> > > out:
> > >
> > > PER_SCOSVR3 = 0x0003 | STICKY_TIMEOUTS |
> > > WHOLE_SECONDS | SHORT_INODE,
> > > PER_OSR5 = 0x0003 | STICKY_TIMEOUTS |
> > > WHOLE_SECONDS, ...
> > > PER_BSD = 0x0006,
> > > PER_SUNOS = 0x0006 | STICKY_TIMEOUTS,
> > >
> > > But I can certainly just make it a stand-alone file with just the
> > > bitfield. Or, I can still do the conversion and ignore PER_OSR5 and
> > > PER_SUNOS.
> >
> > well.. if "you" as kernel can't really make out what it is, how is poor
> > userspace supposed to do it ?
>
> Kernel should just print with %lx and leave pretty-printing to
> luserspace.
I would tend to agree with this -- I don't want to fill the kernel with
string-dumping case statements. (Though I have a different patch that
does this, if anyone actually wants it.)
> And name should be /proc/*/personality (obviously :-)
>
> Assuming anybody cares about personalities at all.
I do. :)
--
Kees Cook
Ubuntu Security Team
next prev parent reply other threads:[~2008-10-05 10:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 21:14 [PATCH] proc: add "personality" to process status file Kees Cook
2008-10-02 22:46 ` Randy.Dunlap
2008-10-02 22:56 ` Kees Cook
2008-10-04 21:40 ` Alexey Dobriyan
2008-10-04 21:51 ` Arjan van de Ven
2008-10-04 22:02 ` Kees Cook
2008-10-04 23:42 ` Arjan van de Ven
2008-10-05 0:42 ` Kees Cook
2008-10-05 0:48 ` Arjan van de Ven
2008-10-05 9:11 ` Alexey Dobriyan
2008-10-05 10:07 ` Kees Cook [this message]
2008-10-05 10:14 ` [PATCH v2] proc: show personality via /proc/pid/personality Kees Cook
2008-10-05 23:20 ` Alexey Dobriyan
2008-10-07 13:39 ` Michael Kerrisk
2008-10-07 16:14 ` Kees Cook
2008-10-08 2:45 ` Michael Kerrisk
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=20081005100701.GQ10632@outflux.net \
--to=kees.cook@canonical.com \
--cc=adobriyan@gmail.com \
--cc=arjan@infradead.org \
--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