From: Matt Mackall <mpm@selenic.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Chris Wright <chrisw@osdl.org>,
"Jack O'Quin" <jack.oquin@gmail.com>,
Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org,
Paul Davis <paul@linuxaudiosystems.com>,
Con Kolivas <kernel@kolivas.org>,
rlrevell@joe-job.com
Subject: Re: 2.6.11-rc3-mm2
Date: Fri, 11 Feb 2005 09:37:51 -0800 [thread overview]
Message-ID: <20050211173751.GK15058@waste.org> (raw)
In-Reply-To: <20050211095327.GB6229@elte.hu>
On Fri, Feb 11, 2005 at 10:53:27AM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <mpm@selenic.com> wrote:
>
> > On Fri, Feb 11, 2005 at 09:59:42AM +0100, Ingo Molnar wrote:
> > >
> > > think of SCHED_FIFO on the desktop as an ugly wart, a hammer, that
> > > destroys the careful balance of priorities of SCHED_OTHER tasks. Yes, it
> > > can be useful if you _need_ a scheduling guarantee due to physical
> > > constraints, and it can be useful if the hardware (or the kernel) cannot
> > > buffer enough, but otherwise, it only causes problems.
> >
> > Agreed. I think something short of full SCHED_FIFO will make most
> > desktop folks happy. [...]
>
> ah, but it's not the desktop folks who have to be happy but users :-)
> Really, if you ask any app designer then obviously 'the more CPU time we
> get for sure, the better our app behaves'. So in that sense SCHED_OTHER
> is a fair playground: if you behave nicely you'll have higher priority
> and shorter latencies.
>
> (there are things like SCHED_ISO but how good of a solution they are is
> not yet clear.)
>
> > [...] But a) we still have to figure out exactly how to do that and b)
> > we still have to make everyone else happy. The embedded folks (me
> > included) would prefer to not run our realtime bits as root too..
>
> you dont have to - you can drop root after startup.
>
> > > but i'm not sure how rlimits will contain the whole problem - can
> > > rlimits be restricted to a single app (jackd)?
> >
> > Yes. There's also the whole soft limit thing.
>
> i'm curious, how does this 'per-app' rlimit thing work? If a user has
> jackd installed and runs it from X unprivileged, how does it get the
> elevated rlimit?
It needs a setuid launcher. It would be nice to be able to elevate the
rlimits of running processes but the API doesn't exist yet.
>From the POV of accidental elevation to RT, soft limits are
sufficient. But we can't stop a user from exploiting an app they own
with RT privileges from elevating other apps via ptrace+exec or
whatever. Nor with RT-LSM.
> (while the rest of his desktop still runs with a safe
> rlimit.) SELinux/RT-LSM could do this, but i'm not sure about how
> rlimits give this to you.
How does it get done with RT-LSM? Setgid binaries? It only
discriminates on a group granularity. Or are you saying "and SELinux"
rather than "or SELinux"?
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-02-11 17:45 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 20:51 2.6.11-rc3-mm2 Jack O'Quin
2005-02-11 0:04 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 0:47 ` 2.6.11-rc3-mm2 Chris Wright
2005-02-11 2:09 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 2:22 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11 3:26 ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11 3:41 ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11 5:04 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11 6:34 ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11 6:42 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11 5:09 ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11 6:57 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 7:54 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 8:25 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 8:48 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 8:58 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 9:01 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 9:04 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 9:27 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:49 ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11 19:42 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 19:57 ` 2.6.11-rc3-mm2 Lee Revell
2005-02-11 8:14 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 8:22 ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-11 8:41 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 8:59 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 9:40 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 9:53 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 17:37 ` Matt Mackall [this message]
2005-02-11 17:49 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 20:10 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:45 ` 2.6.11-rc3-mm2 Paul Davis
2005-02-14 5:21 ` 2.6.11-rc3-mm2 Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 13:35 ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-10 20:01 ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-12 22:43 ` 2.6.11-rc3-mm2 Olaf Dietsche
2005-02-10 22:13 ` 2.6.11-rc3-mm2 Corey Minyard
2005-02-10 22:42 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
2005-02-10 23:02 ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 23:31 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
2005-02-10 23:17 ` 2.6.11-rc3-mm2 Adrian Bunk
2005-02-11 16:29 ` 2.6.11-rc3-mm2 Yuval Tanny
2005-02-12 14:53 ` 2.6.11-rc3-mm2 Henning Rohde
2005-02-14 13:22 ` 2.6.11-rc3-mm2 Stefano Rivoir
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=20050211173751.GK15058@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=hch@infradead.org \
--cc=jack.oquin@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul@linuxaudiosystems.com \
--cc=rlrevell@joe-job.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