[Mesa-dev] Texture object locking

[Jason Ekstrand]

Hello all,

Kristian and I were looking at this today, and there seems to be a
substantial race in the way that we are doing texture locking.  In
particular, we usually do the following:

Lock the hashmap
Find the texture object
Unlock the hashmap
Lock the texture object
Do Stuff
Unlock the texture object

As one particular example, _mesa_DeleteTextures does this in
src/mesa/main/texobj.c:1208.  The problem is that the texture could be
deleted in between unlocking the texture map and locking the texture
object.  Is there something I'm missing here?  If not, how bad a problem is
this?

Thanks,
--Jason Ekstrand
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20140606/4aa76802/attachment.html>