From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/3] drm/i915: Mark i915_request.timeline as a volatile, rcu pointer
Date: Thu, 19 Sep 2019 12:23:44 -0000 [thread overview]
Message-ID: <20190919122344.23915.66559@emeril.freedesktop.org> (raw)
In-Reply-To: <20190919111912.21631-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [v2,1/3] drm/i915: Mark i915_request.timeline as a volatile, rcu pointer
URL : https://patchwork.freedesktop.org/series/66923/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.6.0
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)
+
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-19 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 11:19 [PATCH v2 1/3] drm/i915: Mark i915_request.timeline as a volatile, rcu pointer Chris Wilson
2019-09-19 11:19 ` [PATCH v2 2/3] drm/i915: Lock signaler timeline while navigating Chris Wilson
2019-09-19 11:19 ` [PATCH v2 3/3] drm/i915: Protect timeline->hwsp dereferencing Chris Wilson
2019-09-19 12:22 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/3] drm/i915: Mark i915_request.timeline as a volatile, rcu pointer Patchwork
2019-09-19 12:23 ` Patchwork [this message]
2019-09-19 12:44 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-19 13:02 ` [PATCH v2 1/3] " Tvrtko Ursulin
2019-09-19 13:26 ` Chris Wilson
2019-09-19 17:11 ` Tvrtko Ursulin
2019-09-19 17:49 ` Chris Wilson
2019-09-20 8:47 ` Tvrtko Ursulin
2019-09-19 20:09 ` ✓ Fi.CI.IGT: success for series starting with [v2,1/3] " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190919122344.23915.66559@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.