From: Thomas Hellstrom Date: Wed, 18 Dec 2013 13:13:29 +0000 (+0100) Subject: drm/ttm: ttm object security fixes for render nodes X-Git-Tag: v3.14-rc1~47^2~37^2~3 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=05efb1abecce6e36457ae1a7be29ded7ac52292a;p=pandora-kernel.git drm/ttm: ttm object security fixes for render nodes When a client looks up a ttm object, don't look it up through the device hash table, but rather from the file hash table. That makes sure that the client has indeed put a reference on the object, or in gem terms, has opened the object; either using prime or using the global "name". To avoid a performance loss, make sure the file hash table entries can be looked up from under an RCU lock, and as a consequence, replace the rwlock with a spinlock, since we never need to take it in read mode only anymore. Finally add a ttm object lookup function for the device hash table, that is intended to be used when we put a ref object on a base object or, in gem terms, when we open the object. Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul --- Reading git-diff-tree failed