Re: pidns memory leak

From: Cedric Le Goater
Date: Tue Nov 03 2009 - 04:24:50 EST


On 11/03/2009 09:41 AM, Eric W. Biederman wrote:
> Cedric Le Goater <legoater@xxxxxxx> writes:
>
>> On 11/02/2009 11:47 PM, Andrew Morton wrote:
>>> On Mon, 2 Nov 2009 16:38:18 -0600
>>> "Serge E. Hallyn" <serue@xxxxxxxxxx> 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?

yes, it frees a few more dentries, but not enough.

I did:

$ echo 2 > /proc/sys/vm/drop_caches

before :

size-64 193243 198088 88 44 1
dentry 110584 111202 280 14 1
inode_cache 107543 107543 4096 1 1
size-128 56341 63450 152 25 1
size-4096 21107 21107 4096 1 1
vm_area_struct 11838 11960 192 20 1
size-256 11406 11424 280 14 1
size-32 9408 9916 56 67 1
size-512 7710 7710 4096 1 1
sysfs_dir_cache 5288 5328 104 37 1
pid_2 302 336 136 28 1
pid_namespace 1 1 4096 1 1
nsproxy 1 53 72 53 1

after:

size-64 193150 198044 88 44 1
dentry 110509 111202 280 14 1
inode_cache 107543 107543 4096 1 1
size-128 56326 63450 152 25 1
size-4096 21107 21107 4096 1 1
vm_area_struct 11857 11960 192 20 1
size-256 11405 11424 280 14 1
size-32 9408 9916 56 67 1
size-512 7710 7710 4096 1 1
sysfs_dir_cache 5288 5328 104 37 1
pid_2 302 336 136 28 1
pid_namespace 1 1 4096 1 1
nsproxy 1 53 72 53 1


I'll come back to you (daniel or me) when we've nailed this one with a simpler
program. it shows up when stressing the system with lxc containers.

Cheers,

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