mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Max Kellermann <mk@cm4all.com>
Cc: cgroups@vger.kernel.org, cyphar@cyphar.com, lizefan@huawei.com,
	hannes@cmpxchg.org, max@duempel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup_pids: add fork limit
Date: Tue, 10 Nov 2015 10:12:23 -0500	[thread overview]
Message-ID: <20151110151223.GA17938@mtj.duckdns.org> (raw)
In-Reply-To: <144716440621.20175.1000688899886388119.stgit@rabbit.intern.cm-ag>

On Tue, Nov 10, 2015 at 03:06:46PM +0100, Max Kellermann wrote:
> This patch introduces a new setting called "fork_remaining".  When
> positive, each successful fork decrements the value, and once it
> reaches zero, no further forking is allowed, no matter how many of
> those processes are still alive.  The special value "unlimited"
> disables the fork limit.
> 
> The goal of this limit is to have another safeguard against fork
> bombs.  It gives processes a chance to set up their child processes /
> threads, but will be stopped once they attempt to waste resources by
> continuously exiting and cloning new processes.  This can be useful
> for short-lived processes such as CGI programs.

But what's the resource here?  All first-order resources which can be
consumed by forking repeatedly already have proper controllers.
What's the point of adding an extra second-order controller?  Where do
we go from there?  Limit on the number of syscalls?

Thanks.

-- 
tejun

  reply	other threads:[~2015-11-10 15:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 14:06 Max Kellermann
2015-11-10 15:12 ` Tejun Heo [this message]
2015-11-10 15:37   ` Max Kellermann
2015-11-10 15:44     ` Tejun Heo
2015-11-10 17:06     ` Max Kellermann
2015-11-10 17:29       ` Tejun Heo
2015-11-10 17:52         ` Max Kellermann
2015-11-10 15:25 ` Aleksa Sarai
2015-11-10 15:58   ` Austin S Hemmelgarn
2015-11-10 16:19     ` Parav Pandit
2015-11-10 19:54       ` Austin S Hemmelgarn
2015-11-15 13:36         ` Aleksa Sarai
2015-11-16 17:02           ` Austin S Hemmelgarn
2015-11-10 16:01   ` Max Kellermann

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=20151110151223.GA17938@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=cyphar@cyphar.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=max@duempel.org \
    --cc=mk@cm4all.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

all inboxes | Powered by JetHome®