From: Randy Dunlap <rdunlap@xenotime.net>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
Vasiliy Kulikov <segoon@openwall.com>,
Dan Ballard <dan@mindstab.net>, Jiri Kosina <jkosina@suse.cz>,
Al Viro <viro@zeniv.linux.org.uk>,
Stephen Wilson <wilsons@start.ca>,
David Rientjes <rientjes@google.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Eric Paris <eparis@redhat.com>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] sysctl: control functionality of /proc/pid/mem
Date: Sat, 21 Jan 2012 10:27:37 -0800 [thread overview]
Message-ID: <4F1B0399.5000801@xenotime.net> (raw)
In-Reply-To: <20120121090644.GA31670@www.outflux.net>
On 01/21/2012 01:06 AM, Kees Cook wrote:
> Add the "proc_pid_mem" sysctl to control whether or not /proc/pid/mem is
> allowed to work: 0: disabled, 1: read only, 2: read/write.
Maybe mention that the default is 2 (or did you mean to change that sooner
or later?).
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> Documentation/sysctl/kernel.txt | 14 ++++++++++++++
> fs/proc/base.c | 14 +++++++++++++-
> kernel/sysctl.c | 14 ++++++++++++++
> 3 files changed, 41 insertions(+), 1 deletions(-)
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2012-01-21 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 9:06 [PATCH v2] sysctl: control functionality of /proc/pid/mem Kees Cook
2012-01-21 18:27 ` Randy Dunlap [this message]
2012-01-23 14:41 ` Eric W. Biederman
2012-01-23 18:12 ` 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=4F1B0399.5000801@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dan@mindstab.net \
--cc=eparis@redhat.com \
--cc=jkosina@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rientjes@google.com \
--cc=segoon@openwall.com \
--cc=serge.hallyn@canonical.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wilsons@start.ca \
/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.