On Llu, 2004-07-26 at 22:09, Jon Smirl wrote:
--- Keith Whitwell [EMAIL PROTECTED] wrote:
Additionally, by making this step root-only, the X server is
effectively
required to perform this task, meaning that the client must be
'blessed' by
the X server's security mechanisms, whatever
--- 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
--- Keith Whitwell [EMAIL PROTECTED] wrote:
Additionally, by making this step root-only, the X server is
effectively
required to perform this task, meaning that the client must be
'blessed' by
the X server's security mechanisms, whatever they might be.
I would like to change this from
Jon Smirl wrote:
Context creation in DRM is marked as needing root access. Is this to
prevent a process from doing a DOS attack by creating too many
contexts? Couldn't I do the same DOS attack simply by creating lots of
processes each with their own context?
Is there a hardware limit on contexts?
Context creation in DRM is marked as needing root access. Is this to
prevent a process from doing a DOS attack by creating too many
contexts? Couldn't I do the same DOS attack simply by creating lots of
processes each with their own context?
Is there a hardware limit on contexts? It looks to me
