linux-kernel - Re: [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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6599ad830907141043s1c16d5c9saad9118c210ecef4@mail.gmail.com>
Date:	Tue, 14 Jul 2009 10:43:56 -0700
From:	Paul Menage <menage@...gle.com>
To:	Benjamin Blum <bblum@...gle.com>
Cc:	balbir@...ux.vnet.ibm.com, lizf@...fujitzu.com,
	containers@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org,
	libcg-devel <libcg-devel@...ts.sourceforge.net>,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 0/2] CGroups: cgroup member list enhancement/fix

On Tue, Jul 14, 2009 at 10:34 AM, Benjamin Blum<bblum@...gle.com> wrote:
> procs file). While that's preferable to a global lock, if we can add a
> field to task_struct, a (lockless) flag-based approach might be
> possible.
>

I've been trying to think of a way to do that. AFAICS the only way to
do that reliably would be to move the call to cgroup_fork() that hooks
into the parent's cgroup inside the lock on the group leader's thread
list, and move the fork callbacks into cgroup_fork(). (Which would
mean that they'd not be able to sleep/fail, etc).

Paul
--
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/