-----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. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDC2UmX1gOwKyEAw8RArVVAKCUqkLLjCc0r3EkW5HrKDqbAZTRAgCfcCF6 Iam+OSVg2EOiNOY39EhlkYA= =P5mt -----END PGP SIGNATURE----- ------------------------------------------------------- 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
