linux-kernel - Re: [PATCH] Add cgroup support for enabling controllers at boot time

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: <alpine.DEB.1.00.0803070055020.3470@chino.kir.corp.google.com>
Date:	Fri, 7 Mar 2008 00:56:33 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Paul Menage <menage@...gle.com>
cc:	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Pavel Emelianov <xemul@...nvz.org>,
	Hugh Dickins <hugh@...itas.com>,
	Sudhir Kumar <skumar@...ux.vnet.ibm.com>,
	YAMAMOTO Takashi <yamamoto@...inux.co.jp>, lizf@...fujitsu.com,
	linux-kernel@...r.kernel.org, taka@...inux.co.jp,
	linux-mm@...ck.org,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [PATCH] Add cgroup support for enabling controllers at boot
 time

On Fri, 7 Mar 2008, Paul Menage wrote:

> >  Since the command line is logically delimited by spaces, you can
> >  accidently disable a subsystem if its name appears in any of your kernel
> >  options following your cgroup_disable= option.
> 
> I think that you're confusing this with things like the very early
> memory init setup parameters, which do operate on the raw commandline.
> 
> By the time anything is passed to a __setup() function, it's already
> been split into separate strings at space boundaries.
> 

Ok, so the cgroup_disable= parameter should be a list of subsystem names 
delimited by anything other than a space that the user wants disabled.  
That makes more sense, thanks.
--
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/