[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1ljiogfun.fsf@fess.ebiederm.org>
Date: Tue, 03 Nov 2009 00:41:36 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Cedric Le Goater <legoater@...e.fr>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"Serge E. Hallyn" <serue@...ibm.com>, andrea@...share.com,
Linux Containers <containers@...ts.osdl.org>,
Daniel Lezcano <dlezcano@...ibm.com>,
Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
Emelianov <xemul@...nvz.org>,
Alexey Dobriyan <adobriyan@...l.ru>,
linux-kernel@...r.kernel.org
Subject: Re: pidns memory leak
Cedric Le Goater <legoater@...e.fr> writes:
> On 11/02/2009 11:47 PM, Andrew Morton wrote:
>> On Mon, 2 Nov 2009 16:38:18 -0600
>> "Serge E. Hallyn" <serue@...ibm.com> wrote:
>>
>>>> This bug hasn't been fixed yet, has it?
>>>
>>> Well Suka did trace the bug to commit 7766755a2f249e7, and posted a patch
>>> to revert that, acked by Eric on Oct 20. Suka, were you going to repost
>>> that patch?
>>
>> Ah. OK. Thanks. Found it in the backlog pile.
>
> We've added the patch to our patchset and we confirm that the pid_* leaks have
> been reduced to 'nearly' nothing but we still have a lot of inodes and dentries
> leaks. I hope to find some time to investigate and reproduce with a small
> scenario, we are running a LTP like testsuite in a container environment.
Does forcing a cache flush help with the other leaks?
Eric
--
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/
Powered by blists - more mailing lists