All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Kees Cook <kees.cook@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: add "personality" to process status file
Date: Sat, 4 Oct 2008 17:48:43 -0700	[thread overview]
Message-ID: <20081004174843.6fe48a8e@infradead.org> (raw)
In-Reply-To: <20081005004233.GL10632@outflux.net>

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 ?



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-10-05  0:48 UTC|newest]

Thread overview: 18+ 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 [this message]
2008-10-05  9:11           ` Alexey Dobriyan
2008-10-05 10:07             ` Kees Cook
2008-10-05 10:14             ` [PATCH v2] proc: show personality via /proc/pid/personality Kees Cook
2008-10-05 23:20               ` Alexey Dobriyan
     [not found]               ` <20081005101438.GR10632-oSa+0FWJbaXR7s880joybQ@public.gmane.org>
2008-10-07 13:39                 ` Michael Kerrisk
2008-10-07 13:39                   ` Michael Kerrisk
2008-10-07 16:14                   ` Kees Cook
     [not found]                     ` <20081007161422.GD10357-oSa+0FWJbaXR7s880joybQ@public.gmane.org>
2008-10-08  2:45                       ` Michael Kerrisk
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=20081004174843.6fe48a8e@infradead.org \
    --to=arjan@infradead.org \
    --cc=kees.cook@canonical.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 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.