From: Daniel Lezcano <dlezcano@fr.ibm.com>
To: Pavel Emelianov <xemul@openvz.org>,
Sukadev Bhattiprolu <sukadev@us.ibm.com>
Cc: Linux Containers <containers@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: pidns memory leak
Date: Fri, 02 Oct 2009 14:27:04 +0200 [thread overview]
Message-ID: <4AC5F198.2070407@fr.ibm.com> (raw)
Hi,
I am facing a problem with the pid namespace when I launch the following
lxc commands:
lxc-execute -n foo sleep 3600 &
ls -al /proc/$(pidof lxc-init)/exe && lxc-stop -n foo
All the processes related to the container are killed, but there is
still a refcount on the pid_namespace which is never released.
That can be verified in /proc/slabinfo. Running a test suite with
thousand of tests quickly exhaust the memory and the oom killer is
triggered.
Reproduced with a 2.6.31 vanilla kernel on i686 and x86_64 architecture.
Thanks
-- Daniel
next reply other threads:[~2009-10-02 12:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 12:27 Daniel Lezcano [this message]
2009-10-06 4:05 ` pidns memory leak 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
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=4AC5F198.2070407@fr.ibm.com \
--to=dlezcano@fr.ibm.com \
--cc=containers@lists.osdl.org \
--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).