From: Lee Revell <rlrevell@joe-job.com>
To: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
Cc: Arjan van de Ven <arjan@infradead.org>,
Esben Nielsen <nielsen.esben@googlemail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Where is RLIMIT_RT_CPU?
Date: Sat, 15 Jul 2006 11:44:44 -0400 [thread overview]
Message-ID: <1152978284.16617.7.camel@mindpipe> (raw)
In-Reply-To: <1152975857.6374.65.camel@idefix.homelinux.org>
On Sun, 2006-07-16 at 01:04 +1000, Jean-Marc Valin wrote:
> > as long as you can fork and exec as many of those processes as you want
> > a per process rlimit is useless security wise... an evil user just fires
> > off a second process just before the first one gets killed and a non-RT
> > root still is starved out.
>
> Of course, which is why the idea is for the limit to be global, across
> all non-root users. AFAIK, that's what Ingo's original (pre-2.6.12)
> patch did and also what Con Kolivas' SCHED_ISO patch does. That's also
> why I think it would be very hard (if possible at all) to do this in
> user space.
I don't think it's a problem. If the admin does not want non-root users
to be able to lock up the machine, just don't put them in the realtime
group.
Lee
next prev parent reply other threads:[~2006-07-15 15:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 0:23 Where is RLIMIT_RT_CPU? Jean-Marc Valin
2006-07-13 16:43 ` Lee Revell
2006-07-14 9:39 ` Jean-Marc Valin
2006-07-14 21:31 ` Esben Nielsen
2006-07-14 23:20 ` Jean-Marc Valin
2006-07-15 13:58 ` Lee Revell
2006-07-15 14:19 ` Jean-Marc Valin
2006-07-15 14:42 ` Arjan van de Ven
2006-07-15 15:04 ` Jean-Marc Valin
2006-07-15 15:44 ` Lee Revell [this message]
2006-07-16 0:23 ` Jean-Marc Valin
2006-07-16 10:44 ` Esben Nielsen
2006-07-16 10:14 ` Jean-Marc Valin
2006-07-16 12:20 ` Esben Nielsen
2006-07-17 11:53 ` Jean-Marc Valin
2006-07-17 13:59 ` Steven Rostedt
2006-07-17 14:32 ` Jean-Marc Valin
2006-07-17 15:06 ` Steven Rostedt
2006-07-17 16:18 ` Esben Nielsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1152978284.16617.7.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=Jean-Marc.Valin@USherbrooke.ca \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nielsen.esben@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox