Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 19 Sep 2011 18:13:12 +0300
From: Pekka Enberg <>
To: Vasiliy Kulikov <>
Cc: Andrew Morton <>,, 
	Kees Cook <>, Cyrill Gorcunov <>, Al Viro <>, 
	Christoph Lameter <>, Matt Mackall <>,,, Dan Rosenberg <>, Theodore Tso <>, 
	Alan Cox <>, Jesper Juhl <>, 
	Linus Torvalds <>
Subject: Re: Re: [RFC PATCH 2/2] mm: restrict access to /proc/slabinfo

Hi Vasiliy,

On Mon, Sep 19, 2011 at 5:46 PM, Vasiliy Kulikov <> wrote:
>> and
>> concluded that it's not worth it doesn't really protect from anything
> Closing only slabinfo doesn't add any significant protection against
> kernel heap exploits per se, no objections here.
> But as said in the desciption, the reason for this patch is not protecting
> against exploitation heap bugs.  It is a source of infoleaks of kernel
> and userspace activity, which should be forbidden to non-root users.

Last time we discussed this, the 'extra protection' didn't seem to be
significant enough to justify disabling an useful kernel debugging
interface by default.

What's different about the patch now?

>> and causes harm to developers.
> One note: only to _kernel_ developers.  It means it is a strictly
> debugging feature, which shouldn't be enabled in the production systems.

It's pretty much _the_ interface for debugging kernel memory leaks in
production systems and we ask users for it along with /proc/meminfo
when debugging many memory management related issues. When we
temporarily dropped /proc/slabinfo with the introduction of SLUB, people
complained pretty loudly.

I'd be willing to consider this patch if it's a config option that's not enabled
by default; otherwise you need to find someone else to merge the patch.
You can add some nasty warnings to the Kconfig text to scare the users
into enabling it. ;-)


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.