[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 19 Sep 2011 22:33:14 +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 9:55 PM, Vasiliy Kulikov <segoon@...nwall.com> wrote:
> Is there another way to get directly or indirectly the information about
> slabs?
I didn't check closely but there seems to be some filesystem specific
stats under /proc at least. No idea how useful those are as attack
vectors.
I also suspect there are per-module knobs under /proc and /sys that
can be used to get indirect information. Many subsystems have
implemented their own slab wrappers in the past and they keep popping
up every now and then.
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.
