linux-kernel - Re: [PATCH 00/10] Containers(V10): Generic Process 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]

Message-Id: <20070530001455.45cf1dc5.akpm@linux-foundation.org>
Date:	Wed, 30 May 2007 00:14:55 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	menage@...gle.com
Cc:	dev@...ru, xemul@...ru, serue@...ibm.com, vatsa@...ibm.com,
	ebiederm@...ssion.com, haveblue@...ibm.com,
	svaidy@...ux.vnet.ibm.com, balbir@...ibm.com, pj@....com,
	cpw@....com, ckrm-tech@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org, containers@...ts.osdl.org,
	mbligh@...gle.com, rohitseth@...gle.com, devel@...nvz.org
Subject: Re: [PATCH 00/10] Containers(V10): Generic Process Containers

On Tue, 29 May 2007 06:01:04 -0700 menage@...gle.com wrote:

> This is an update to my multi-hierarchy multi-subsystem generic
> process containers patch.
> 
> ...
> 
> Still TODO:
> 
> ...
>
> - lots more testing
> 

So how do we do this?

Is there any sneaky way in which we can modify the kernel so that this new
code gets exercised more?  Obviously, tossing init into some default
system-wide container would be a start.  But I wonder if we can be
sneakier - for example, create a new container on each setuid(), toss the
task into that.  Or something along those lines?
-
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/