linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cedric Le Goater <legoater@free.fr>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Serge E. Hallyn" <serue@us.ibm.com>,
	andrea@cpushare.com, Linux Containers <containers@lists.osdl.org>,
	Daniel Lezcano <dlezcano@fr.ibm.com>,
	Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
	Emelianov <xemul@openvz.org>, Alexey Dobriyan <adobriyan@mail.ru>,
	linux-kernel@vger.kernel.org
Subject: Re: pidns memory leak
Date: Tue, 03 Nov 2009 10:24:39 +0100	[thread overview]
Message-ID: <4AEFF6D7.9080509@free.fr> (raw)
In-Reply-To: <m1ljiogfun.fsf@fess.ebiederm.org>

On 11/03/2009 09:41 AM, Eric W. Biederman wrote:
> Cedric Le Goater <legoater@free.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@us.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?

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.

      reply	other threads:[~2009-11-03  9:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 12:27 pidns memory leak Daniel Lezcano
2009-10-06  4:05 ` Sukadev Bhattiprolu
2009-10-06  8:18   ` Daniel Lezcano
2009-10-08  3:08     ` Sukadev Bhattiprolu
2009-10-08  8:11       ` Daniel Lezcano
2009-10-09  3:29         ` Sukadev Bhattiprolu
2009-10-09 13:18           ` Daniel Lezcano
2009-10-09 20:38             ` Sukadev Bhattiprolu
2009-10-09 20:50               ` Eric W. Biederman
2009-10-10  1:58                 ` Sukadev Bhattiprolu
2009-10-10  2:08                   ` Eric W. Biederman
2009-10-09 21:54             ` Matt Helsley
2009-10-10  1:32             ` Sukadev Bhattiprolu
2009-10-12  8:41               ` Daniel Lezcano
2009-10-14  6:15                 ` Sukadev Bhattiprolu
2009-11-02 21:33                   ` Andrew Morton
2009-11-02 22:38                     ` Serge E. Hallyn
2009-11-02 22:47                       ` Andrew Morton
2009-11-03  7:24                         ` Cedric Le Goater
2009-11-03  8:41                           ` Eric W. Biederman
2009-11-03  9:24                             ` Cedric Le Goater [this message]

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=4AEFF6D7.9080509@free.fr \
    --to=legoater@free.fr \
    --cc=adobriyan@mail.ru \
    --cc=akpm@linux-foundation.org \
    --cc=andrea@cpushare.com \
    --cc=containers@lists.osdl.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=xemul@openvz.org \
    /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;
as well as URLs for NNTP newsgroup(s).