linux-kernel - Re: [PATCH 1/9] [RFC] Support named cgroups hierarchies

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: <6599ad830907020119g68abedbeu19ef46f32c4f6f3d@mail.gmail.com>
Date:	Thu, 2 Jul 2009 01:19:30 -0700
From:	Paul Menage <menage@...gle.com>
To:	Louis.Rilling@...labs.com
Cc:	lizf@...fujitsu.com, balbir@...ux.vnet.ibm.com,
	containers@...ts.linux-foundation.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/9] [RFC] Support named cgroups hierarchies

On Thu, Jul 2, 2009 at 1:09 AM, Louis Rilling<Louis.Rilling@...labs.com> wrote:
>
> I did not see anything preventing two hierarchies from having the same
> (non empty) name.

If you try to mount with a name that matches an already existing
hierarchy, and you leave the subsystem options empty or give options
that match the existing mount, then you get the original mount; if you
specify conflicting options you get an error. I don't think the code
will let you have two hierarchies with the same non-empty name.

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/