diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2017-11-21 14:06:52 +0300 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2017-11-22 00:44:55 +0300 |
| commit | f9eb63b98c91f4cfaddf54b769f971c77da10917 (patch) | |
| tree | 7ade4d8aa0c6b2dc3d1bed58239228d1209aeb1a /drivers/xen | |
| parent | cff109f06dfebc379a5a36d49b541212caaec607 (diff) | |
| download | linux-f9eb63b98c91f4cfaddf54b769f971c77da10917.tar.xz | |
drm/i915/selftests: Avoid drm_gem_handle_create under struct_mutex
Despite us reloading the module around every selftest, the lockclasses
persist and the chains used in selftesting may then dictate how we are
allowed to nest locks during runtime testing. As such we have to be just
as careful, and in particular it turns out we are not allowed to nest
dev->object_name_lock (drm_gem_handle_create) inside dev->struct_mutex.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103830
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20171121110652.1107-1-chris@chris-wilson.co.uk
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Diffstat (limited to 'drivers/xen')
0 files changed, 0 insertions, 0 deletions