From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail203.messagelabs.com (mail203.messagelabs.com [216.82.254.243]) by kanga.kvack.org (Postfix) with ESMTP id 5649D9000BD for ; Mon, 19 Sep 2011 14:46:59 -0400 (EDT) Received: by dyj16 with SMTP id 16so113419dyj.14 for ; Mon, 19 Sep 2011 11:46:56 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20110919175856.GA4282@albatros> References: <20110918170512.GA2351@albatros> <20110919144657.GA5928@albatros> <20110919155718.GB16272@albatros> <20110919161837.GA2232@albatros> <20110919173539.GA3751@albatros> <20110919175856.GA4282@albatros> Date: Mon, 19 Sep 2011 21:46:55 +0300 Message-ID: Subject: Re: [kernel-hardening] Re: [RFC PATCH 2/2] mm: restrict access to /proc/slabinfo From: Pekka Enberg Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: To: Vasiliy Kulikov Cc: Andrew Morton , kernel-hardening@lists.openwall.com, Kees Cook , Cyrill Gorcunov , Al Viro , Christoph Lameter , Matt Mackall , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Dan Rosenberg , Theodore Tso , Alan Cox , Jesper Juhl , Linus Torvalds On Mon, Sep 19, 2011 at 8:58 PM, Vasiliy Kulikov wrote: >> Isn't this >> much stronger protection especially if you combine that with /proc/slabinfo >> restriction? > > I don't see any reason to change allocators if we close slabinfo. OK, so what about /proc/meminfo, sysfs, 'perf kmem', and other kernel interfaces through which you can get direct or indirect information about kernel memory allocations? Pekka -- 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: email@kvack.org