| 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: <490FF8D0.1070607@cn.fujitsu.com> Date: Tue, 04 Nov 2008 15:25:04 +0800 From: Li Zefan <lizf@...fujitsu.com> To: Paul Menage <menage@...gle.com> CC: Matt Helsley <matthltc@...ibm.com>, Andrew Morton <akpm@...ux-foundation.org>, "Rafael J. Wysocki" <rjw@...k.pl>, Linux-Kernel <linux-kernel@...r.kernel.org>, Linux Containers <containers@...ts.linux-foundation.org>, linux-pm@...ts.linux-foundation.org, Cedric Le Goater <clg@...ibm.com>, "Serge E. Hallyn" <serue@...ibm.com> Subject: Re: [PATCH 3/5] Container Freezer: Implement freezer cgroup subsystem Paul Menage wrote: > On Mon, Nov 3, 2008 at 10:12 PM, Li Zefan <lizf@...fujitsu.com> wrote: >> I think another reasonable and easier way is to disable writing freezer.state >> of top cgroup, so we can skip checks in freezer_fork() for tasks in top cgroup. >> > > Yes, if freezing the root cgroup isn't needed then that is definitely > simpler - I wasn't sure if Matt wanted to be able to freeze the root > group with this subsystem. > If someone just mounts the freezer subsystem and freeze the root cgroup, all the tasks will be freezed, and then seems all he can do is reset the machine (or do a suspend/resume). That's why I think it's reasonable to disable it. -- 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