Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1109190841580.8771@router.home>
Date: Mon, 19 Sep 2011 08:42:46 -0500 (CDT)
From: Christoph Lameter <cl@...two.org>
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>,
  Pekka Enberg <penberg@...nel.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 Sun, 18 Sep 2011, Vasiliy Kulikov wrote:

> > Reviewed-by: Kees Cook <kees@...ntu.com>
>
> Looks like the members of the previous slabinfo discussion don't object
> against the patch now and it got two other Reviewed-by responses.  Can
> you merge it as-is or should I probably convince someone else?

The patch is incomplete. If you want to restrict access to this
information then /sys/kernel/slab needs to have a similar
restriction.


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.