public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasiliy Kulikov <segoon@openwall.com>
To: Hugh Dickins <hughd@google.com>
Cc: kernel-hardening@lists.openwall.com,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	"H. Peter Anvin" <hpa@zytor.com>, Greg KH <greg@kroah.com>,
	Theodore Tso <tytso@mit.edu>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	James Morris <jmorris@namei.org>, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [RFC v2 2/3] procfs: add hidepid= and gid= mount options
Date: Thu, 8 Dec 2011 23:21:43 +0400	[thread overview]
Message-ID: <20111208192143.GB9794@albatros> (raw)
In-Reply-To: <alpine.LSU.2.00.1112051451470.3938@sister.anvils>

Hi Hugh,

On Mon, Dec 05, 2011 at 14:55 -0800, Hugh Dickins wrote:
> On Sat, 19 Nov 2011, Vasiliy Kulikov wrote:
> > This patch adds support of mount options to restrict access to
> > /proc/PID/ directories.  The default backward-compatible "relaxed"
> > behaviour is left untouched.
> 
> This patch, in 3.2.0-rc3-next-20111202, leaks tasks: watch
> while :; do ps; grep KernelStack /proc/meminfo; sleep 1; done

Thank you very much for the report!

Unfortunately, I have no time to look at it now, will try to debug the
issue these weekends.

Thanks,

-- 
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments

  reply	other threads:[~2011-12-08 19:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-19 11:01 [RFC v2 1/3] procfs: parse mount options Vasiliy Kulikov
2011-11-19 11:02 ` [RFC v2 2/3] procfs: add hidepid= and gid= " Vasiliy Kulikov
2011-12-05 22:55   ` Hugh Dickins
2011-12-08 19:21     ` Vasiliy Kulikov [this message]
2011-11-19 11:02 ` [RFC v2 3/3] procfs: add documentation for procfs " Vasiliy Kulikov
2011-11-22  0:34 ` [RFC v2 1/3] procfs: parse " Andrew Morton
2011-11-22 10:07   ` Vasiliy Kulikov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111208192143.GB9794@albatros \
    --to=segoon@openwall.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=hughd@google.com \
    --cc=jmorris@namei.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox