--- Alan Cox <[EMAIL PROTECTED]> wrote:
> > I would like to change this from root+authorized to just authorized
> in
> > the DRM drivers. In the mesa-solo model context's don't need to
> pass
> > through the root priv server.
>
> You would need to do a full audit of that code path, especially with
> regards to resource consumption and limits.
I haven't located any code in the Xserver preventing me from making
1000's of processes and asking for a context from each one. So I think
the resource limit hole is there for X too.
What's the right fix for this? I could add code to DRM to count the
active contexts and just refuse to make any more after there are 100
active ones.
I suspect some of the other existing non-root but authorized DRM entry
points can be used to allocate memory without limit. For example I
don't know what would happen if you tried to create a million single
byte textures.
=====
Jon Smirl
[EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
