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

> Non-root RT tasks are not "unprivileged" - they have a level of
> privileges between a normal user and root.  Really I think it's OK for
> these tasks to consume 100% CPU, as the admin has explicitly allowed it.

Sure, if the admin has allowed it, but I think it's also OK for desktop
users to have access to rt scheduling by default, as long as their tasks
are "well-behaved" (i.e. only use a few percent CPU).

> The only problem is that Ubuntu shipped with this enabled for everyone.

The problem is not the fact that it's enabled, but the fact that the
amount of CPU allowed isn't restricted.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ