linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Daniel Lezcano <dlezcano@fr.ibm.com>
Cc: Pavel Emelianov <xemul@openvz.org>,
	Sukadev Bhattiprolu <sukadev@us.ibm.com>,
	Linux Containers <containers@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pidns memory leak
Date: Wed, 7 Oct 2009 20:08:28 -0700	[thread overview]
Message-ID: <20091008030828.GA18973@us.ibm.com> (raw)
In-Reply-To: <4ACAFD6A.3060008@fr.ibm.com>

Still digging through some traces, but below I have some questions that 
I am still trying to answer.

>
> I am not sure what you mean by 'struct pids' but what I observed is:

Ok, I see that too. If pids leak, then pid-namespace will leak too.
Do you see any leaks in proc_inode_cache ?

>
> pid_2 and pid_namespace (as they are named in /proc/slabinfo) are never  
> decremented.
>
>> And the pid_namespace does not seem to reproduce for me, with out the
>> 'ls -al /proc/...' above, or with the simpler 'ns_exec' approach to
>> creating pid namespace.
>
> I tried to write a simpler program but I failed to reproduce it.
>
>> I am going through the code for lxc-execute, but does it remount /proc  
>> in the container ?
>
> Right, the parent does a clone(NEWMNT|NEWPID|NEWIPC|NEWUTS), wait for  
> the child while this one (pid 1) 'execs' the lxc-init process. This  
> program mounts /proc and fork-exec the command passed as parameter (here  
> 'sleep 3600').
>
> Without this intermediate process, the leak *seems* not happening.
>
> If you don't access /proc/<pid>/<file>, the leak is not happening.

I could not see the code for that.  Does lxc-stop unmount /proc too ?
Or is the umount expected to happen automatically after all processes
in the container are killed ?

Sukadev

  reply	other threads:[~2009-10-08  3:08 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 [this message]
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

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=20091008030828.GA18973@us.ibm.com \
    --to=sukadev@linux.vnet.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sukadev@us.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).