From: Andrew Morton <akpm@linux-foundation.org>
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
WANG Cong <xiyou.wangcong@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Wu Fengguang <fengguang.wu@intel.com>,
Dan Carpenter <error27@gmail.com>, Tejun Heo <tj@kernel.org>
Subject: Re: [RFC Patch] kcore: restrict access to the whole memory
Date: Wed, 22 Dec 2010 15:02:09 -0800 [thread overview]
Message-ID: <20101222150209.8e18afa7.akpm@linux-foundation.org> (raw)
In-Reply-To: <1293016926-1714-1-git-send-email-amwang@redhat.com>
On Wed, 22 Dec 2010 19:21:59 +0800
Amerigo Wang <amwang@redhat.com> wrote:
> This patch restricts /proc/kcore from accessing the whole memory,
> instead, only an ELF header can be read.
>
> The initial patch was done by Vivek.
Getting a bit tired of this.
Are we supposed to be mind-readers? How else are we to work out why
you think Linux needs this feature? What problems it solves? What
applications are expected to break and what the breakage patterns are?
Why the benefits are worth the maintenance costs and the risk of
breakage? Why it's done with a config option and not a boot-time or
runtime tunable?
c'mon, you guys have been around long enough to understand this stuff.
next prev parent reply other threads:[~2010-12-22 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 11:21 [RFC Patch] kcore: restrict access to the whole memory Amerigo Wang
2010-12-22 23:02 ` Andrew Morton [this message]
2010-12-23 10:01 ` Cong Wang
2010-12-23 14:39 ` Eugene Teo
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=20101222150209.8e18afa7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=error27@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=tj@kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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