From: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
To: Robert Gierzinger <robert.gierzinger-RbZlAiThDcE@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: cgroup pid controller side effects
Date: Fri, 16 Oct 2015 10:39:43 -0700 [thread overview]
Message-ID: <20151016173943.GA2162@cmpxchg.org> (raw)
In-Reply-To: <f2e-561fb480-9-1b99f780@25775614>
Hi Robert,
On Thu, Oct 15, 2015 at 04:13:02PM +0200, Robert Gierzinger wrote:
> I have finally had time to test 4.3-rc5 especially (my greatly anticipated) process limitiation with cgroup-pids.
> With bash forkbombs, it really works nice, however, I had some side effects with the forkbomb from
> https://github.com/linux-vserver/util-vserver/blob/master/tests/forkbomb.c
>
> The good thing: my test systems did not die as in previous versions during the simulated attack. But executing the file with e.g.
> ./forkbomb 100000 100 fork
> I get "unable to fork process: Resource temporarily unavailable" on the host
It looks like this forkbomb is not waiting for its children and is
creating a whole lot of zombies.
The pids controller is currently broken in that zombies can escape
accounting completely, and the proposed fix is too invasive to go in
before 4.4. Until then, we need forkbombs to nicely cooperate with us!
Could you retry your test against the following branch?
https://git.kernel.org/cgit/linux/kernel/git/tj/cgroup.git/log/?h=for-4.4
Thanks!
Johannes
next prev parent reply other threads:[~2015-10-16 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 14:13 cgroup pid controller side effects Robert Gierzinger
2015-10-16 17:39 ` Johannes Weiner [this message]
[not found] ` <20151016173943.GA2162-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2015-10-19 10:00 ` Robert Gierzinger
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=20151016173943.GA2162@cmpxchg.org \
--to=hannes-druugvl0lcnafugrpc6u6w@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robert.gierzinger-RbZlAiThDcE@public.gmane.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