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: <6599ad830707171126o7c431277p84f532d0122a8a98@mail.gmail.com>
Date:	Tue, 17 Jul 2007 11:26:03 -0700
From:	"Paul (宝瑠) Menage" 
	<menage@...gle.com>
To:	balbir@...ux.vnet.ibm.com
Cc:	dhaval@...ux.vnet.ibm.com, "Pavel Emelianov" <xemul@...ru>,
	"linux kernel mailing list" <linux-kernel@...r.kernel.org>,
	"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:
> without too much knowledge of each other. BTW, what are the semantics
> of css_put() is it expected to free the container/run the release agent
> when the reference count of the container_subsys_state drops to zero?
>

If you css_put() the last reference on a subsystem state object and
the associated container is marked as notify_on_release, then
check_for_release() is called which does a more full check of whether
the container is releasable. If it is, a workqueue task is scheduled
to run the userspace release agent, which can then do anything it
wants, including potentially deleting the empty container.

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/