|
Message-ID: <CAOJsxLFdNVnW6Faap0UaqZQDQxbA_dEiR2HGdzZtGMJFsVR1WQ@mail.gmail.com> Date: Mon, 19 Sep 2011 21:46:55 +0300 From: Pekka Enberg <penberg@...helsinki.fi> To: Vasiliy Kulikov <segoon@...nwall.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, kernel-hardening@...ts.openwall.com, Kees Cook <kees@...ntu.com>, Cyrill Gorcunov <gorcunov@...il.com>, Al Viro <viro@...iv.linux.org.uk>, Christoph Lameter <cl@...ux-foundation.org>, Matt Mackall <mpm@...enic.com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org, Dan Rosenberg <drosenberg@...curity.com>, Theodore Tso <tytso@....edu>, Alan Cox <alan@...ux.intel.com>, Jesper Juhl <jj@...osbits.net>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: Re: [RFC PATCH 2/2] mm: restrict access to /proc/slabinfo On Mon, Sep 19, 2011 at 8:58 PM, Vasiliy Kulikov <segoon@...nwall.com> 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
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.