[PATCH 02/29] drm/i915/execlists: Check for ce->state before destroy

Chris Wilson chris at chris-wilson.co.uk
Sat Jun 23 10:56:58 UTC 2018

As we may cancel the ce->state allocation during context pinning (but
crucially after we mark ce as operational), that means we may be asked
to destroy a nonexistent ce->state. Given the choice in handing a
complex error path on pinning, and just ignoring the lack of state in
destroy, choice the latter for simplicity.

Reported-by: Zhao Yakui <yakui.zhao at intel.com>
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
 drivers/gpu/drm/i915/intel_lrc.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
index 33bc914c2ef5..02ee3b12507f 100644
--- a/drivers/gpu/drm/i915/intel_lrc.c
+++ b/drivers/gpu/drm/i915/intel_lrc.c
@@ -1337,11 +1337,15 @@ static void execlists_schedule(struct i915_request *request,
 static void execlists_context_destroy(struct intel_context *ce)
-	GEM_BUG_ON(!ce->state);
+	if (!ce->state)
+		return;
+	GEM_BUG_ON(i915_gem_object_is_active(ce->state->obj));
-	__i915_gem_object_release_unless_active(ce->state->obj);
+	i915_gem_object_put(ce->state->obj);
 static void execlists_context_unpin(struct intel_context *ce)

More information about the Intel-gfx-trybot mailing list