On Tue, Aug 23, 2005 at 11:04:22AM -0700, Ian Romanick wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Stephane Marchesin wrote: > > > Also, with the current log design for the memory manager, it is possible > > for a rogue process to make the log wrap and not call the > > force_log_update ioctl, thus being able to create some kind of race > > condition where the drm believes it still owns the memory but another > > process has allocated it. > > The log design presents numerous opportunities for rogue processes to do > bad things. At some level, that's inherent in the nature of direct > rendering. If you don't trust the processes, don't enable direct rendering.
Considering one of the major uses for direct rendering is games I don't think that idea will work. -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
