Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 27 Sep 2011 14:35:25 -0500 (CDT)
From: Christoph Lameter <>
To: Vasiliy Kulikov <>
cc:, Pekka Enberg <>,
  Matt Mackall <>,,
  Kees Cook <>, Dave Hansen <>,, Linus Torvalds <>,
  David Rientjes <>, Alan Cox <>,
Subject: Re: [PATCH 1/2] mm: restrict access to slab files under procfs and

On Tue, 27 Sep 2011, Vasiliy Kulikov wrote:

> On Tue, Sep 27, 2011 at 13:08 -0500, Christoph Lameter wrote:
> > Possible candidates:
> >
> > christoph@...y:~/n/linux-2.6$ grep proc_create mm/*
> > mm/swapfile.c:	proc_create("swaps", 0, NULL, &proc_swaps_operations);
> > mm/vmstat.c:	proc_create("buddyinfo", S_IRUGO, NULL, &fragmentation_file_operations);
> > mm/vmstat.c:	proc_create("pagetypeinfo", S_IRUGO, NULL, &pagetypeinfo_file_ops);
> > mm/vmstat.c:	proc_create("vmstat", S_IRUGO, NULL, &proc_vmstat_file_operations);
> > mm/vmstat.c:	proc_create("zoneinfo", S_IRUGO, NULL, &proc_zoneinfo_file_operations);
> >
> > vmstat and zoneinfo in particular give similar information to what is
> > revealed through the slab proc files.
> Do you know whether these files are actively used?  I don't want to
> break tools like "free" or "top".  In this case we'll have to discover
> another way to limit this information.

top uses per process information. Tried an strace and I see no access to
vmstat or zoneinfo.

free uses /proc/meminfo not vmstat or zoneinfo. Since you already have a
patch that limits /proc/meminfo access there is already an issue there.

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.