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 22:55:18 +0400
From: Vasiliy Kulikov <>
To: Pekka Enberg <>
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

On Mon, Sep 19, 2011 at 21:46 +0300, Pekka Enberg wrote:
> 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?

Oh, we also have perf...  Given these are separate interfaces, I think
slab oriented restriction makes more sense.

So, now we have:

'perf kmem' - not sure what specific files should be guarded

Is there another way to get directly or indirectly the information about


Vasiliy Kulikov - bringing security into open computing environments

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.