linux-kernel - Re: [PATCH 2/4] posix-timers: limit the number of posix timers per process

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: <4E5D5EE6.3070708@linux.intel.com>
Date:	Tue, 30 Aug 2011 15:06:30 -0700
From:	Andi Kleen <ak@...ux.intel.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	eric.dumazet@...il.com
Subject: Re: [PATCH 2/4] posix-timers: limit the number of posix timers per
 process


> Sorry, it should be an rlimit from day one, IMO.
>

Ok.

> Partly because rlimits are a better implementation.

The reason I went with a sysctl is that rlimits are more intrusive for 
user space,
requires special tools or patching bash.

> Partly because once rlimits are added, the /proc knob no longer has any
> sane behaviour.  Does it only modify /sbin/init?  Does it do a global
> process walk, modifying all threads?

There's no way to modify: you would need to kill the process or randomly
take timers away. The limit only applies to new timers.

-Andi

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