From: Kees Cook <kees.cook@canonical.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: add "personality" to process status file
Date: Thu, 2 Oct 2008 15:56:24 -0700 [thread overview]
Message-ID: <20081002225624.GK10632@outflux.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0810021544070.26309@shark.he.net>
Heya Randy,
On Thu, Oct 02, 2008 at 03:46:31PM -0700, Randy.Dunlap wrote:
> On Thu, 2 Oct 2008, Kees Cook wrote:
> > There is no sane way to query the personality flags of arbitrary process
> > from userspace. This adds the flags to the /proc/$pid/status file.
>
> The patch seems to be missing an update to Documentation/filesystems/proc.txt !
> Please add that. TIA.
The /proc/pid/status file is "self documenting" (in theory), and doesn't
have separate documentation in proc.txt yet. If I had touched the
"stat" file, I would have included and update, since I was the last to
document that file. ;)
-Kees
--
Kees Cook
Ubuntu Security Team
next prev parent reply other threads:[~2008-10-02 22:56 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 [this message]
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
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=20081002225624.GK10632@outflux.net \
--to=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.