From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754913Ab1I1UoY (ORCPT ); Wed, 28 Sep 2011 16:44:24 -0400 Received: from mga03.intel.com ([143.182.124.21]:50230 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753919Ab1I1UoX (ORCPT ); Wed, 28 Sep 2011 16:44:23 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.68,457,1312182000"; d="scan'208";a="56703044" Date: Wed, 28 Sep 2011 21:52:35 +0100 From: Alan Cox To: Dave Hansen Cc: Christoph Lameter , David Rientjes , Vasiliy Kulikov , kernel-hardening@lists.openwall.com, Pekka Enberg , Matt Mackall , Andrew Morton , linux-mm@kvack.org, Kees Cook , Valdis.Kletnieks@vt.edu, Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] mm: restrict access to /proc/meminfo Message-ID: <20110928215235.05d4f2e5@bob.linux.org.uk> In-Reply-To: <1317241905.16137.516.camel@nimitz> References: <20110927175453.GA3393@albatros> <20110927175642.GA3432@albatros> <20110927193810.GA5416@albatros> <1317241905.16137.516.camel@nimitz> Organization: Intel X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; x86_64-redhat-linux-gnu) Organisation: Intel Corporation UK Ltd, registered no. 1134945 (England), Registered office Pipers Way, Swindon, SN3 1RJ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 28 Sep 2011 13:31:45 -0700 Dave Hansen wrote: > On Tue, 2011-09-27 at 15:47 -0500, Christoph Lameter wrote: > > 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. > > We could also just _effectively_ make it output in MB: > > foo = foo & ~(1<<20) I do not think that does what you intend 8) I do like the idea - it avoids any interfaces vanishing and surprise breakages while only CAP_SYS_whatever needs the real numbers