mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zefan Li <lizefan@huawei.com>
To: <yuzhou@mogujie.com>
Cc: <containers@lists.linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: pidns: Make pid accounting and pid_max per namespace
Date: Sat, 10 Oct 2015 11:35:16 +0800	[thread overview]
Message-ID: <56188774.1040000@huawei.com> (raw)
In-Reply-To: <56179700.3010703@mogujie.com>

On 2015/10/9 18:29, Zhang Haoyu wrote:
> I started multiple docker containers in centos6.6(linux-2.6.32-504.16.2),
> and there's one bad program was running in one container.
> This program produced many child threads continuously without free, so more and
> more pid numbers were consumed by this program, until hitting the pix_max limit (32768
> default in my system ).
>
> What's worse is that containers and host share the pid numbers resource, so new program
> cannot be produced any more in host and other containers.
>
> And, I clone the upstream kernel source from
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> This problem is still there, I'm not sure.
>
> IMO, we should isolate the pid accounting and pid_max between pid namespaces,
> and make them per pidns.
> Below post had request for making pid_max per pidns.
> http://thread.gmane.org/gmane.linux.kernel/1108167/focus=1111210
>

Mainline kernel already supports per-cgroup pid limit, which should solve
your problem.


  reply	other threads:[~2015-10-10  3:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 10:29 Zhang Haoyu
2015-10-10  3:35 ` Zefan Li [this message]
2015-10-10  4:40   ` Zhang Haoyu
2015-10-10  4:46     ` Zhang Haoyu

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=56188774.1040000@huawei.com \
    --to=lizefan@huawei.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuzhou@mogujie.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

Powered by JetHome