linux-kernel - Re: [PATCH 0/9] Containers (V9): 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]

Date:	Sun, 29 Apr 2007 02:37:21 -0700
From:	Paul Jackson <pj@....com>
To:	menage@...gle.com
Cc:	akpm@...ux-foundation.org, dev@...ru, xemul@...ru,
	serue@...ibm.com, vatsa@...ibm.com, ebiederm@...ssion.com,
	haveblue@...ibm.com, svaidy@...ux.vnet.ibm.com, balbir@...ibm.com,
	ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	rohitseth@...gle.com, mbligh@...gle.com, containers@...ts.osdl.org,
	devel@...nvz.org
Subject: Re: [PATCH 0/9] Containers (V9): Generic Process Containers

I'm afraid that this patch set doesn't do cpusets very well.

It builds and boots and mounts the cpuset file system ok.
But trying to write the 'mems' file hangs the system hard.

I had to test it against 2.6.21-rc7-mm2, because I can't boot
2.6.21-rc7-mm1, due to the 'bad_page' problem that I noted in an
earlier post this evening on lkml.

These container patches seemed to apply ok against 2.6.21-rc7-mm2,
and built and booted ok.  I built with an sn2_defconfig configuration,
having the following CONTAINER and CPUSET settings:

    CONFIG_CONTAINERS=y
    CONFIG_CONTAINER_DEBUG=y
    CONFIG_CPUSETS=y
    CONFIG_CONTAINER_CPUACCT=y
    CONFIG_PROC_PID_CPUSET=y
    # CONFIG_ACPI_CONTAINER is not set

I could mount the cpuset file system on /dev/cpuset just fine.

Then I invoked the following commands:

    # cd /dev/cpuset
    # mkdir foo
    # cd foo
    # echo 0-3 > cpus
    # echo 0-1 > mems

At that point, the system hangs.  Reproduced three times, on two boots.
I never get a shell prompt back from that second echo.  I have to hit
Reset.  The three different hangs were done with the following three
different values:

	echo 0-3 > mems
	echo 0-1 > mems
	echo 1 > mems

On that last one, "echo 1 > mems", I did not do the echo to cpus first.

The test system had 8 cpus, numbered 0-7, and 4 mems, numbered 0-3.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.925.600.0401
-
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/