linux-kernel - Re: [RFC][PATCH 13/22] sched: add resource limits for -deadline tasks

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: <1289597455.6525.786.camel@Palantir>
Date:	Fri, 12 Nov 2010 22:30:55 +0100
From:	Raistlin <raistlin@...ux.it>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Chris Friesen <cfriesen@...tel.com>, oleg@...hat.com,
	Frederic Weisbecker <fweisbec@...il.com>,
	Darren Hart <darren@...art.com>,
	Johan Eker <johan.eker@...csson.com>,
	"p.faure" <p.faure@...tech.ch>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Claudio Scordino <claudio@...dence.eu.com>,
	michael trimarchi <trimarchi@...is.sssup.it>,
	Fabio Checconi <fabio@...dalf.sssup.it>,
	Tommaso Cucinotta <cucinotta@...up.it>,
	Juri Lelli <juri.lelli@...il.com>,
	Nicola Manica <nicola.manica@...i.unitn.it>,
	Luca Abeni <luca.abeni@...tn.it>,
	Dhaval Giani <dhaval@...is.sssup.it>,
	Harald Gustafsson <hgu1972@...il.com>,
	paulmck <paulmck@...ux.vnet.ibm.com>
Subject: Re: [RFC][PATCH 13/22] sched: add resource limits for -deadline
 tasks

On Thu, 2010-11-11 at 20:57 +0100, Peter Zijlstra wrote:
> > In fact, this patch:
> >  - adds the resource limit RLIMIT_DLDLINE, which is the minimum value
> >    a user task can use as its own deadline;
> >  - adds the resource limit RLIMIT_DLRTIME, which is the maximum value
> >    a user task can use as it own runtime.
> > 
>
> We might also want to add an additional !SYS_CAP_ADMIN global bandwidth
> cap much like the existing sysctl bandwidth cap.
> 
Mmm... I think we've never discussed much about that before, so here I
am. I'm currently asking one to be root to set SCHED_DEADLINE as his
policy. Normal users are allowed to do so, but just under the rlimits
restrictions provided by this patch.

So, first of all, are we cool with this? Or do we want normal users to
be able to give their tasks SCHED_DEADLINE policy by default? Maybe we
want that but up to a certain bandwidth? Is this that you mean here,
having two bandwidth limits, one of which !SYS_ADMINs could not cross?

Sorry for being annoying, but I've never got any feedback on this, while
I think it's something really important.

Thanks,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
----------------------------------------------------------------------
Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa  (Italy)

http://blog.linux.it/raistlin / raistlin@...ga.net /
dario.faggioli@...ber.org

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)