diff options
| author | Chris Wilson | 2019-06-18 18:19:51 +0200 |
|---|---|---|
| committer | Chris Wilson | 2019-06-18 19:14:43 +0200 |
| commit | eca153603f2f020e15d071918e0daf1d56c17d29 (patch) | |
| tree | 2419428db7c5390302d05648ad8b92e60e2a8032 /drivers/gpu/drm/drm_hashtab.c | |
| parent | drm/i915/selftests: Flush live_evict (diff) | |
| download | kernel-qcow2-linux-eca153603f2f020e15d071918e0daf1d56c17d29.tar.gz kernel-qcow2-linux-eca153603f2f020e15d071918e0daf1d56c17d29.tar.xz kernel-qcow2-linux-eca153603f2f020e15d071918e0daf1d56c17d29.zip | |
drm/i915: Don't dereference request if it may have been retired when printing
This has caught me out on countless occasions, when we retrieve a pointer
from the submission/execlists backend, it does not carry a reference to
the context or ring. Those are only pinned while the request is active,
so if we see the request is already completed, it may be in the process
of being retired and those pointers defunct.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110938
Fixes: 3a068721a973 ("drm/i915: Show ring->start for the ELSP context/request queue")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190618161951.28820-2-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/drm_hashtab.c')
0 files changed, 0 insertions, 0 deletions