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

Message-ID: <6599ad830707172307t7a9f9555n3ebe8c20c8b854fa@mail.gmail.com>
Date:	Tue, 17 Jul 2007 23:07:09 -0700
From:	"Paul (宝瑠) Menage" 
	<menage@...gle.com>
To:	balbir@...ux.vnet.ibm.com
Cc:	dhaval@...ux.vnet.ibm.com,
	"linux kernel mailing list" <linux-kernel@...r.kernel.org>,
	"Pavel Emelianov" <xemul@...ru>, "Paul Jackson" <pj@....com>,
	"Linux Containers" <containers@...ts.osdl.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: Containers: css_put() dilemma

On 7/17/07, Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
>
> Ok.. so my problem still remains, how do I get a non-blocking atomic
> reference increment/decrement routine, that would prevent my
> container from being deleted?

css_put() in my new patchset will be non-blocking.

>
> I don't find cpusets using css_put().

Cpusets never needs to keep a non-process reference on a cpuset
object, so the framework handles everything.

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/