From: Oleg Nesterov <oleg@redhat.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: ebiederm@xmission.com, Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: is pid_namespace leak in v3.10?
Date: Tue, 5 Jul 2016 16:34:52 +0200 [thread overview]
Message-ID: <20160705143452.GA20099@redhat.com> (raw)
In-Reply-To: <577B9CC5.3090404@huawei.com>
On 07/05, Xishi Qiu wrote:
>
> I find pid_namespace leak by "cat /proc/slabinfo | grep pid_namespace".
> The kernel version is RHEL 7.1 (kernel v3.10 stable).
> The following is the test case, after several times, the count of pid_namespace
> become very large, is it correct?
Apparently not,
> I also test mainline, and the count will increase too, but it seems stably later.
And I can't reproduce the problem with the latest rhel7 kernel.
And just in case, I have no idea what actually slub reports as "active_objs" but
certainly this is not the number of allocated "in use" objects, so it is fine if
this counter doesn't go to zero when your test-case exits. But it should not grow
"too much".
> BTW, this patch doesn't help.
> 24c037ebf5723d4d9ab0996433cee4f96c292a4d
> exit: pidns: alloc_pid() leaks pid_namespace if child_reaper is exiting
Sure, it can't help, your test-case doesn't fork other processes which could race
with the exiting sub-namespace init.
> int main()
> {
> pid_t pid, child_pid;
> int i, status;
> void *stack;
>
> for (i = 0; i < 100; i++) {
> stack = malloc(8192);
> pid = clone(&test, (char *)stack + 8192, CLONE_NEWPID|SIGCHLD, 0);
> }
>
> sleep(5);
is this sleep() really needed to trigger the problem?
Oleg.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-07-05 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 11:40 is pid_namespace leak in v3.10? Xishi Qiu
2016-07-05 14:34 ` Oleg Nesterov [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=20160705143452.GA20099@redhat.com \
--to=oleg@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiuxishi@huawei.com \
/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).