[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/i915: Verify the engine after acquiring the active.lock
Patchwork
patchwork at emeril.freedesktop.org
Wed Sep 18 15:16:03 UTC 2019
== Series Details ==
Series: series starting with [1/4] drm/i915: Verify the engine after acquiring the active.lock
URL : https://patchwork.freedesktop.org/series/66867/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: drm/i915: Verify the engine after acquiring the active.lock
Okay!
Commit: drm/i915: Mark i915_request.timeline as a volatile, rcu pointer
+drivers/gpu/drm/i915/gt/intel_timeline.c:504:41: expected struct intel_timeline *tl
+drivers/gpu/drm/i915/gt/intel_timeline.c:504:41: got struct intel_timeline [noderef] <asn:4> *timeline
+drivers/gpu/drm/i915/gt/intel_timeline.c:504:41: warning: incorrect type in initializer (different address spaces)
+drivers/gpu/drm/i915/i915_request.c:771:49: expected struct list_head const *head
+drivers/gpu/drm/i915/i915_request.c:771:49: got struct list_head [noderef] <asn:4> *
+drivers/gpu/drm/i915/i915_request.c:771:49: warning: incorrect type in argument 2 (different address spaces)
+drivers/gpu/drm/i915/i915_request.c:813:9: warning: dereference of noderef expression
Commit: drm/i915: Lock signaler timeline while navigating
-O:drivers/gpu/drm/i915/i915_request.c:771:49: expected struct list_head const *head
-O:drivers/gpu/drm/i915/i915_request.c:771:49: got struct list_head [noderef] <asn:4> *
-O:drivers/gpu/drm/i915/i915_request.c:771:49: warning: incorrect type in argument 2 (different address spaces)
-O:drivers/gpu/drm/i915/i915_request.c:813:9: warning: dereference of noderef expression
+
Commit: drm/i915: Protect timeline->hwsp dereferencing
-O:drivers/gpu/drm/i915/gt/intel_timeline.c:504:41: expected struct intel_timeline *tl
-O:drivers/gpu/drm/i915/gt/intel_timeline.c:504:41: got struct intel_timeline [noderef] <asn:4> *timeline
-O:drivers/gpu/drm/i915/gt/intel_timeline.c:504:41: warning: incorrect type in initializer (different address spaces)
+
More information about the Intel-gfx
mailing list