linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@gentwo.org>
To: David Rientjes <rientjes@google.com>
Cc: Vasiliy Kulikov <segoon@openwall.com>,
	kernel-hardening@lists.openwall.com,
	Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, Kees Cook <kees@ubuntu.com>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	Valdis.Kletnieks@vt.edu,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Alan Cox <alan@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mm: restrict access to /proc/meminfo
Date: Tue, 27 Sep 2011 15:47:24 -0500 (CDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1109271546320.13797@router.home> (raw)
In-Reply-To: <alpine.DEB.2.00.1109271328151.24402@chino.kir.corp.google.com>

On Tue, 27 Sep 2011, David Rientjes wrote:

> It'll turn into another one of our infinite number of capabilities.  Does
> anything actually care about statistics at KB granularity these days?

Changing that to MB may also break things. It may be better to have
consistent system for access control to memory management counters that
are not related to a process.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-09-27 20:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 17:54 [PATCH 1/2] mm: restrict access to slab files under procfs and sysfs Vasiliy Kulikov
2011-09-27 17:56 ` [PATCH 2/2] mm: restrict access to /proc/meminfo Vasiliy Kulikov
2011-09-27 18:27   ` David Rientjes
2011-09-27 19:14     ` Vasiliy Kulikov
2011-09-27 19:38   ` Vasiliy Kulikov
2011-09-27 20:03     ` Christoph Lameter
2011-09-27 20:33       ` David Rientjes
2011-09-27 20:47         ` Christoph Lameter [this message]
2011-09-28 20:31           ` Dave Hansen
2011-09-28 20:52             ` Alan Cox
2011-09-29  0:43             ` Valdis.Kletnieks
2011-09-29 14:11               ` Christoph Lameter
2011-09-29 16:18         ` Vasiliy Kulikov
2011-09-29 16:30           ` Dave Hansen
2011-09-29 16:43             ` [kernel-hardening] " Vasiliy Kulikov
2011-09-29 16:57           ` Valdis.Kletnieks
2011-09-29 17:25             ` [kernel-hardening] " Vasiliy Kulikov
2011-09-29 17:28           ` Vasiliy Kulikov
2011-09-28 21:46     ` Andrew Morton
2011-09-30 19:53       ` Vasiliy Kulikov
2011-09-30 20:03         ` Andrew Morton
2011-09-30 20:12           ` Vasiliy Kulikov
2011-09-30 20:15           ` Dave Hansen
2011-09-27 18:08 ` [PATCH 1/2] mm: restrict access to slab files under procfs and sysfs Christoph Lameter
2011-09-27 19:16   ` Vasiliy Kulikov
2011-09-27 19:35     ` Christoph Lameter
2011-09-27 18:21 ` David Rientjes
2011-09-27 20:00   ` Pekka Enberg

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=alpine.DEB.2.00.1109271546320.13797@router.home \
    --to=cl@gentwo.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=alan@linux.intel.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=kees@ubuntu.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.com \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=segoon@openwall.com \
    --cc=torvalds@linux-foundation.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