From: Colin Walters <walters@verbum.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Randy Dunlap <rdunlap@xenotime.net>,
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 v3] sysctl: control functionality of /proc/pid/mem
Date: Tue, 24 Jan 2012 12:34:33 -0500 [thread overview]
Message-ID: <1327426475.17382.3.camel@lenny> (raw)
In-Reply-To: <20120123212115.GA29641@www.outflux.net>
On Mon, 2012-01-23 at 13:21 -0800, 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 (default).
Both your git commit and the Documentation/ entry are totally missing a
rationale for this. Why would an admin want to set this on or off?
What replaces it, if anything? What are the tradeoffs with its
replacement? What userspace programs might break when this is toggled?
next prev parent reply other threads:[~2012-01-24 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 21:21 [PATCH v3] sysctl: control functionality of /proc/pid/mem Kees Cook
2012-01-24 11:03 ` Vasiliy Kulikov
2012-01-24 11:12 ` Alexey Dobriyan
2012-01-24 11:51 ` Vasiliy Kulikov
2012-01-31 19:22 ` Kees Cook
2012-01-24 17:34 ` Colin Walters [this message]
2012-01-25 23:30 ` Andrew Morton
2012-01-26 4:22 ` Eric W. Biederman
2012-01-31 19:26 ` 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=1327426475.17382.3.camel@lenny \
--to=walters@verbum.org \
--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=rdunlap@xenotime.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).