linux-kernel - Re: [PATCH] Re: [RFC PATCH] namespaces: fix leak on fork() failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 04 May 2012 10:19:31 +0200
From:	Mike Galbraith <efault@....de>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Pavel Emelyanov <xemul@...allels.com>,
	Cyrill Gorcunov <gorcunov@...nvz.org>,
	Louis Rilling <louis.rilling@...labs.com>
Subject: Re: [PATCH]  Re: [RFC PATCH] namespaces: fix leak on fork() failure

On Fri, 2012-05-04 at 01:03 -0700, Eric W. Biederman wrote: 
> Mike Galbraith <efault@....de> writes:

> > Hm.  echo 3 > /proc/sys/vm/drop_caches.. *poof gone*
> 
> Good to hear.  I am sad to hear that proc_flush_task isn't doing a
> better job but at least memory pressure will now free everything up as
> it is supposed to.
> 
> > Grr.  I wonder who is doing the pinning when I don't monitor, but..
> >
> > <patch>
> > kick kick kick... it's dead Jim.
> > </patch>
> 
> Are you saying all known bugs are fixed?  Thanks for digging into this
> by the way.  A fresh set of eyeballs is always nice.

Think so.  I'm beating it up in our 3.0 kernel with all fixes, since the
patch that started this odyssey got backported to that kernel as well.

Too bad I had so much ftrace trouble, I chased a dead bug for a week :)

-Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/