linux-kernel - Re: [Patch 01/05]- Containers: Documentation on using containers

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]

Date:	Tue, 19 Sep 2006 11:32:19 -0400
From:	Valdis.Kletnieks@...edu
To:	rohitseth@...gle.com
Cc:	Andrew Morton <akpm@...l.org>, devel@...nvz.org,
	CKRM-Tech <ckrm-tech@...ts.sourceforge.net>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Patch 01/05]- Containers: Documentation on using containers

On Thu, 14 Sep 2006 18:38:33 PDT, Rohit Seth said:

(Sorry for the late reply...)

> --- linux-2.6.18-rc6-mm2.org/Documentation/containers.txt	1969-12-31 16:00:00.000000000 -0800
> +++ linux-2.6.18-rc6-mm2.ctn/Documentation/containers.txt	2006-09-14 17:13:48.000000000 -0700

> +5- Remove a task from container
> +	echo <pid> rmtask

echo <pid> > rmtask

is what I think was intended.  Also, I'm not sure <pid> is the best
meta-syntax - anybody got a better idea?

> +9- Freeing a container
> +	cd /mnt/configfs/containers/
> +	rmdir test_container

What happens if you try to remove a container that still has active tasks? Are
you relying on the VFS to catch the 'non-empty directory'? (of course, 'rm -r'
has predictable semantics here).

I see support for "add a task" and "remove a task", but none for listing
the current tasks in the container?

Content of type "application/pgp-signature" skipped