Thomas Hellstrom 05efb1abec 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 <thellstrom@vmware.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
2014-01-08 10:11:57 +01:00
..
2010-08-10 08:20:20 +10:00
2013-11-06 13:36:18 +10:00
2013-08-19 10:32:26 +10:00
2012-11-28 18:36:05 +10:00
2012-05-31 17:49:26 -07:00
2013-12-17 18:09:43 +01:00
2013-08-07 10:16:50 +10:00
2013-12-18 11:35:45 +10:00
2013-12-17 18:09:46 +01:00
2013-05-23 12:51:32 +02:00
2011-02-07 13:09:42 +10:00
2013-12-18 11:43:29 +10:00
2012-03-10 13:06:04 +00:00
2013-11-08 18:09:36 +01:00