linux-kernel - Re: [RFC PATCH V2] Enforce RSS+Swap rlimit

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]

Date:	Tue, 15 Nov 2011 19:02:49 -0500
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	jmarchan@...hat.com
CC:	bsingharora@...il.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [RFC PATCH V2] Enforce RSS+Swap rlimit

On 11/15/2011 8:10 AM, Jerome Marchand wrote:
> 
> Change since V1: rebase on 3.2-rc1
> 
> Currently RSS rlimit is not enforced. We can not forbid a process to exceeds
> its RSS limit and allow it swap out. That would hurts the performance of all
> system, even when memory resources are plentiful.
> 
> Therefore, instead of enforcing a limit on rss usage alone, this patch enforces
> a limit on rss+swap value. This is similar to memsw limits of cgroup.
> If a process rss+swap usage exceeds RLIMIT_RSS max limit, he received a SIGBUS
> signal. 

No good idea.
 - RLIMIT_RSS has clear definition and this patch break it. you should makes
   another rlimit at least.
 - SIGBUS can be ignored. rlimit shouldn't ignorable.


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