On Mon, Sep 19, 2011 at 21:46 +0300, Pekka Enberg wrote: > On Mon, Sep 19, 2011 at 8:58 PM, Vasiliy Kulikov <segoon@xxxxxxxxxxxx> 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: /proc/slabinfo /sys/kernel/slab /proc/meminfo 'perf kmem' - not sure what specific files should be guarded Is there another way to get directly or indirectly the information about slabs? Thanks, -- Vasiliy Kulikov http://www.openwall.com - bringing security into open computing environments -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. 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: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>