linux-kernel - Re: Where is RLIMIT_RT

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: <1152919240.6374.38.camel@idefix.homelinux.org>
Date:	Sat, 15 Jul 2006 09:20:40 +1000
From:	Jean-Marc Valin <Jean-Marc.Valin@...erbrooke.ca>
To:	Esben Nielsen <nielsen.esben@...glemail.com>
Cc:	Lee Revell <rlrevell@...-job.com>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: Where is RLIMIT_RT_CPU?

> Can't you just make a prio 1 task which signals a prio 99 once say every 
> second. If the priority 99 task doesn't get the signal after say 2 
> seconds, it will look for a rt task running wild. At worst it will have to do
> an O(n) algorith when things have gone wrong, not when everything is 
> working.

Well, that would work in sort of preventing a complete lockup, but the
watchdog wouldn't even know if the task eating lots of CPU is privileged
(OK) or unprivileged (not OK). Also, the original RLIMIT_RT_CPU feature
allowed you to really control how much CPU is available to unprivileged
users, not just prevent them from getting 100% CPU. 

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