linux-kernel - [PATCH 0/8] memcg, cgroup: kill css

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 8 Apr 2013 16:19:53 +0800
From:	Li Zefan <lizefan@...wei.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Tejun Heo <tj@...nel.org>, Glauber Costa <glommer@...allels.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Michal Hocko <mhocko@...e.cz>,
	Johannes Weiner <hannes@...xchg.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Cgroups <cgroups@...r.kernel.org>, <linux-mm@...ck.org>
Subject: [PATCH 0/8] memcg, cgroup: kill css_id

(This patchset depends on "memcg: make memcg's life cycle the same as cgroup")

This patchset converts memcg to always use cgroup->id, and then kills
css_id.

As we've removed memcg's own refcnt, converting memcg to use cgroup->id
is very straight-forward.

Li Zefan (8):
      cgroup: implement cgroup_is_ancestor()
      cgroup: implement cgroup_from_id()
      memcg: convert to use cgroup_is_ancestor()
      memcg: convert to use cgroup_from_id()
      memcg: convert to use cgroup->id
      memcg: fail to create cgroup if the cgroup id is too big
      memcg: don't use css_id any more
      cgroup: kill css_id

--
 include/linux/cgroup.h |  44 ++-------
 kernel/cgroup.c        | 302 +++++++++-----------------------------------------------------
 mm/memcontrol.c        |  53 ++++++-----
 3 files changed, 77 insertions(+), 322 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/