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: <6599ad830902031114t7de1b570p4ed5ec497e2e150e@mail.gmail.com>
Date:	Tue, 3 Feb 2009 11:14:03 -0800
From:	Paul Menage <menage@...gle.com>
To:	sean finney <seanius@...nius.net>
Cc:	Gustavo Noronha <kov@...ian.org>, debian-devel@...ts.debian.org,
	linux-kernel@...r.kernel.org
Subject: Re: cgroup mount point

On Tue, Feb 3, 2009 at 10:51 AM, sean finney <seanius@...nius.net> wrote:
> On Tue, Feb 03, 2009 at 07:49:15PM +0100, Mike Hommey wrote:
>> > Having one virtual filesystem mounted on top of another virtual
>> > filesystem seems like a recipe for problems.
>>
>> Like with /sys/fs/fuse/connections ? Come on, there is no problem with a
>> virtual filesystem mounted on top of another.
>
> or /proc/bus/usb or /dev/shm or /dev/pts... :)
>

/dev is a bit different though - even if it's mounted as a udev fs,
you can create a new directory in there to act as a mount point.

Cgroups supports multiple hierarchies on different mount points.

So if you have two cgroups hierarchies - say one for CPU/network and
one for memory isolation, you could create /dev/cgroup/cpunet and
/dev/cgroup/memory and mount the two hierarchies. But sysfs doesn't
allow you to create new subdirectories to act as mountpoints. If we
can have a /sys/cgroups directory which allows you to create arbitrary
subdirs to act as mountpoints, that could be OK.

Or just fake it by mounting a tmpfs on /sys/cgroups and then create
mount points in there, but that seems like a bit of a hack.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ