linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aleksa Sarai <cyphar@cyphar.com>
To: tj@kernel.org, lizefan@huawei.com, mingo@redhat.com,
	peterz@infradead.org
Cc: richard@nod.at, fweisbec@gmail.com, linux-kernel@vger.kernel.org,
	cgroups@vger.kernel.org, Aleksa Sarai <cyphar@cyphar.com>
Subject: [PATCH v7 0/4] cgroups: add pids subsystem
Date: Wed,  1 Apr 2015 13:31:26 +1100	[thread overview]
Message-ID: <1427855490-5280-1-git-send-email-cyphar@cyphar.com> (raw)

This is a futher revised version of the pids v6 patchset[1]. The main
changes include:

* Actually separate the subsystem callback bitmasks for use with
  for_each_subsys_which(needs_*_callback, ...). Also switch from the
  usage of explicit ss_mask checking with for_each_subsys() with
  for_each_subsys_which().

* Pass an opaque cgroup_fork_state structure between the
  cgroup_{can,cancel,post}_fork hooks which stores the current
  task_struct's css_set. The refcount bumping and dropping is handled
  within cgroup_cfs_{get,put}() respectively. This is done so that
  the internal implementation of cgroup_fork_state is not exposed to
  copy_process(), while also allowing the caller to decide when they
  want to snapshot the current css_set.

* Fix a bug where migrating a task between cgroup hierachies would not
  decrement pids.counter in the source hierarchy. This would cause
  limits to be enforced prematurely due to residual charges on the pid
  counter. This is done by adding a detach() callback that alerts a
  subsystem to a task detaching from it.

[1]: https://lkml.org/lkml/2015/3/14/2

Aleksa Sarai (4):
  cgroups: use bitmask to filter for_each_subsys
  cgroups: replace explicit ss_mask checking with for_each_subsys_which
  cgroups: allow a cgroup subsystem to reject a fork
  cgroups: implement the PIDs subsystem

 include/linux/cgroup.h        |  42 +++++-
 include/linux/cgroup_subsys.h |   4 +
 init/Kconfig                  |  16 +++
 kernel/Makefile               |   1 +
 kernel/cgroup.c               | 244 ++++++++++++++++++++++++++-------
 kernel/cgroup_pids.c          | 310 ++++++++++++++++++++++++++++++++++++++++++
 kernel/fork.c                 |  38 +++++-
 7 files changed, 596 insertions(+), 59 deletions(-)
 create mode 100644 kernel/cgroup_pids.c

-- 
2.3.4


             reply	other threads:[~2015-04-01  2:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01  2:31 Aleksa Sarai [this message]
2015-04-01  2:31 ` [PATCH v7 1/4] cgroups: use bitmask to filter for_each_subsys Aleksa Sarai
2015-04-01  2:31 ` [PATCH v7 2/4] cgroups: replace explicit ss_mask checking with for_each_subsys_which Aleksa Sarai
2015-04-01  2:31 ` [PATCH v7 3/4] cgroups: allow a cgroup subsystem to reject a fork Aleksa Sarai
2015-04-01  2:31 ` [PATCH v7 4/4] cgroups: implement the PIDs subsystem Aleksa Sarai
2015-04-01  2:36 ` [PATCH v7 0/4] cgroups: add pids subsystem Aleksa Sarai
2015-04-01  2:40   ` Tejun Heo

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=1427855490-5280-1-git-send-email-cyphar@cyphar.com \
    --to=cyphar@cyphar.com \
    --cc=cgroups@vger.kernel.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=richard@nod.at \
    --cc=tj@kernel.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).