summaryrefslogtreecommitdiffstats
path: root/drivers/bluetooth/hci_h5.c
diff options
context:
space:
mode:
authorOscar Mateo <oscar.mateo@intel.com>2014-05-16 14:20:43 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2014-05-16 16:24:39 +0200
commit19656430a874132a1d79c56387a6eec1ef9a5689 (patch)
tree30f04ee74dedb780372e4e77a885903ab1c0ccef /drivers/bluetooth/hci_h5.c
parent4271b753bb77443f232ff1f96f4530ea2b322fd3 (diff)
downloadblackbird-op-linux-19656430a874132a1d79c56387a6eec1ef9a5689.tar.gz
blackbird-op-linux-19656430a874132a1d79c56387a6eec1ef9a5689.zip
drm/i915: Gracefully handle obj not bound to GGTT in is_pin_display
Otherwise, we do a NULL pointer dereference. I've seen this happen while handling an error in i915_gem_object_pin_to_display_plane(): If i915_gem_object_set_cache_level() fails, we call is_pin_display() to handle the error. At this point, the object is still not pinned to GGTT and maybe not even bound, so we have to check before we dereference its GGTT vma. The IGT kms_flip/bo-too-big tests for this bug. v2: Chris Wilson says restoring the old value is easier, but that is_pin_display is useful as a theory of operation. Take the solomonic decision: at least this way is_pin_display is a little more robust (until Chris can kill it off). v3: Chris suggests the WARN in i915_gem_obj_to_ggtt has outlived its usefulness: add a reminder to remove it. Issue: VIZ-3772 Signed-off-by: Oscar Mateo <oscar.mateo@intel.com> Testcase: igt/kms_flip/bo-too-big Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/bluetooth/hci_h5.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud