[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] [request for inclusion] Realtime LSM
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Date: Fri, 7 Jan 2005 22:10:59 +0000
- Mail-followup-to: Christoph Hellwig <hch@xxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, Lee Revell <rlrevell@xxxxxxxxxxx>, paul@xxxxxxxxxxxxxxxxxxxxx, arjanv@xxxxxxxxxx, mingo@xxxxxxx, chrisw@xxxxxxxx, alan@xxxxxxxxxxxxxxxxxxx, joq@xxxxxx, linux-kernel@xxxxxxxxxxxxxxx
- References: <200501071620.j07GKrIa018718@localhost.localdomain> <1105132348.20278.88.camel@krustophenia.net> <20050107134941.11cecbfc.akpm@osdl.org>
- User-agent: Mutt/1.4.1i
On Fri, Jan 07, 2005 at 01:49:41PM -0800, Andrew Morton wrote:
> Chris Wright <chrisw@xxxxxxxx> wrote:
> >
> > ...
> > Last I checked they could be controlled separately in that module. It
> > has been suggested (by me and others) that one possible solution would
> > be to expand it to be generic for all caps.
>
> Maybe this is the way?
It's at least not as bad as the current hack (when properly done in
the capabilities modules instead of adding one ontop).
I must say I'm not exactly happy with that idea still. It ties the
privilegues we have been separating from a special uid (0) to filesystem
permissions again. It's not nessecarily a bad idea per, but it doesn't
really fit into the model we've been working to. I'd expect quite a few
unpleasant devices when a user detects that the distibution had been
binding various capabilities to uids/gids behinds his back.
So to make forward progress I'd like the audio people to confirm whether
the mlock bits in 2.6.9+ do help that half of their requirement first
(and if not find a way to fix it) and then tackle the scheduling part.
For that one I really wonder whether the combination of the now actually
working nicelevels (see Mingo's post) and a simple wrapper for the really
high requirements cases doesn't work.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
References: