linux-kernel - [PATCH 0/2] CGroups: cgroup member list enhancement/fix

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]

Message-ID: <20090702231814.3969.44308.stgit@menage.mtv.corp.google.com>
Date:	Thu, 02 Jul 2009 16:26:15 -0700
From:	Paul Menage <menage@...gle.com>
To:	lizf@...fujitzu.com, serue@...ibm.com, akpm@...ux-foundation.org
Cc:	containers@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, bblum@...gle.com
Subject: [PATCH 0/2] CGroups: cgroup member list enhancement/fix

The following series (written by Ben Blum) adds a "cgroup.procs" file
to each cgroup that reports unique tgids rather than pids, and fixes a
pid namespace bug in the existing "tasks" file that could cause
readers in different namespaces to interfere with one another.

The patches as a pair provide similar functionality to Li Zefan's
patch posted yesterday, with the addition on the "cgroup.procs" file;
if it's decided that Li's patch needs to be fast-tracked to 2.6.31,
then these patches can be rebased as a small extension of Li's patch;
if Li'z patch doesn't need to go to 2.6.31 then it makes more sense to
take this pair since they provide more overall functionality.

---

Ben Blum (2):
      Adds a read-only "procs" file similar to "tasks" that shows only unique tgids
      Ensures correct concurrent opening/reading of pidlists across pid namespaces

 include/linux/cgroup.h |   46 +++++-
 kernel/cgroup.c        |  355 +++++++++++++++++++++++++++++++++---------------
 2 files changed, 285 insertions(+), 116 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/