linux-kernel - Re: [PATCH v2 2/2] cgroups: add an nproc subsystem

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 9 Mar 2015 09:49:45 +0800
From:	Zefan Li <lizefan@...wei.com>
To:	Tejun Heo <tj@...nel.org>
CC:	Aleksa Sarai <cyphar@...har.com>, <mingo@...hat.com>,
	<peterz@...radead.org>, <richard@....at>, <fweisbec@...il.com>,
	<linux-kernel@...r.kernel.org>, <cgroups@...r.kernel.org>
Subject: Re: [PATCH v2 2/2] cgroups: add an nproc subsystem

Hi Tejun,

On 2015/3/2 23:22, Tejun Heo wrote:
> Hello,
> 
> On Fri, Feb 27, 2015 at 03:17:19PM +1100, Aleksa Sarai wrote:
>> +config CGROUP_NPROC
>> +	bool "Process number limiting on cgroups"
>> +	depends on PAGE_COUNTER
>> +	help
>> +	  This options enables the setting of process number limits in the scope
>> +	  of a cgroup. Any attempt to fork more processes than is allowed in the
>> +	  cgroup will fail. This allows for more basic resource limitation that
>> +	  applies to a cgroup, similar to RLIMIT_NPROC (except that instead of
>> +	  applying to a process tree it applies to a cgroup).
> 
> Please reflect the rationale from this discussion thread in the commit
> message and help text.  Also, I'd much prefer to name it pids
> controller after the resource it's controlling.
> 

Seems we are going to accept this feature. Is it because kmemcg won't be able
to fullfill this requirement? And that's because kmemcg can only and will only
be able to control global kernel memory usage? 

I thought there will be some control file like kmem.pids.max, which will
translate the number of processes to the kernel memory needed, and fail memory
allocation if we reach the limit, for example make task_struct slab return
NULL.

--
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/