From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kees Cook <kees@outflux.net>,
arjan@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: maps protection
Date: Sat, 10 Mar 2007 18:55:07 -0600 [thread overview]
Message-ID: <20070311005507.GC10459@waste.org> (raw)
In-Reply-To: <20070310162101.716b6b57.akpm@linux-foundation.org>
On Sat, Mar 10, 2007 at 04:21:01PM -0800, Andrew Morton wrote:
> > On Sat, 10 Mar 2007 10:33:41 -0800 Kees Cook <kees@outflux.net> wrote:
> > Here's another revision, with both the "can ptrace" and the global /proc
> > knob;
>
> We'd be needing a changelog for that.
>
> Please update the procfs documentation.
>
> Does the patch also cover /proc/pid/smaps?
Also, we ought to revisit /proc/pid/mem write, which is currently disabled.
Either drop the code, fix it, or make it root only.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2007-03-11 1:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070307012234.GN9621@outflux.net>
[not found] ` <20070306175609.267bd7a9.akpm@linux-foundation.org>
[not found] ` <20070307021335.GR9621@outflux.net>
[not found] ` <20070306185942.585e7cd1.akpm@linux-foundation.org>
2007-03-07 3:14 ` [PATCH] proc: maps protection Kees Cook
2007-03-07 4:22 ` Arjan van de Ven
2007-03-08 20:55 ` Kees Cook
2007-03-10 2:30 ` Andrew Morton
2007-03-10 5:01 ` Arjan van de Ven
2007-03-10 18:33 ` Kees Cook
2007-03-11 0:21 ` Andrew Morton
2007-03-11 0:55 ` Matt Mackall [this message]
2007-03-11 1:43 ` Kees Cook
2007-03-11 1:55 ` Kees Cook
2007-03-12 17:20 ` [PATCH] getrusage() : Fill ru_inblock and ru_oublock fields if possible Eric Dumazet
2007-03-10 1:37 ` [PATCH] proc: maps protection Andy Isaacson
2007-03-05 20:15 Kees Cook
2007-03-06 0:23 ` Kees Cook
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=20070311005507.GC10459@waste.org \
--to=mpm@selenic.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=kees@outflux.net \
--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