| 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
| ||
|
Message-ID: <6599ad830707171055ua1e1135ief95a5ff3cf9dfc9@mail.gmail.com> Date: Tue, 17 Jul 2007 10:55:52 -0700 From: "Paul (宝瑠) Menage" <menage@...gle.com> To: "Paul Jackson" <pj@....com> Cc: balbir@...ux.vnet.ibm.com, dhaval@...ux.vnet.ibm.com, xemul@...ru, linux-kernel@...r.kernel.org, containers@...ts.osdl.org, akpm@...ux-foundation.org Subject: Re: Containers: css_put() dilemma On 7/17/07, Paul Jackson <pj@....com> wrote: > > At least for cpusets (the mother of all containers), notify on release > is part of the user visible API of cpusets. The kernel does not remove > cpusets; it runs a user program, /sbin/cpuset_release_agent. That > program might choose to rmdir the cpuset directory, and/or do other > actions, like notify a batch scheduler that one of its cpusets was > released. Right, that's what the release agent patch for process containers does - there's a file in the hierarchy root called "release_agent" that contains the path to the program to run if a notify_on_release container goes idle. When you mount the "cpuset" filesystem, it automatically populates that file with "/sbin/cpuset_release_agent". A workqueue task is used to actually do the notifications so that references can be dropped without having to potentially run a userspace helper. 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/
Powered by blists - more mailing lists