linux-kernel - Re: [RFC] cgroups: Resource controller for open files.

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>] [day] [month] [year] [list]

Date:	Wed, 2 Jul 2014 10:49:01 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Binder Makin <merimus@...gle.com>
Cc:	viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org,
	Daniel Jacobowitz <dmj@...gle.com>,
	Johannes Weiner <hannes@...xchg.org>,
	Michal Hocko <mhocko@...e.cz>, Li Zefan <lizefan@...wei.com>,
	cgroups@...r.kernel.org
Subject: Re: [RFC] cgroups: Resource controller for open files.

Hello,

On Wed, Jul 02, 2014 at 10:46:59AM -0400, Binder Makin wrote:
> kmem keeps the cgroup from DOSing the machine but then you can get a ENOMEM
> out of some call which is trying to allocate kernel memory.
> People are used to limiting file handles from rlimits and the EMFILE is
> easier for them to debug/fix.

EMFILE instead of ENOMEM seems really thin as the sole rationale for a
whole new controller, doesn't it?

Thanks.

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