summaryrefslogtreecommitdiffstats
path: root/COPYING
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2010-07-23 23:18:51 +0100
committerEric Anholt <eric@anholt.net>2010-08-01 19:56:29 -0700
commit8dc1775dce10d5e47d2805665804fddf39ea3a90 (patch)
treec8929cedb667faacd988eb22312dbe7c72728c0a /COPYING
parentbe72615bcf4d5b7b314d836c5e1b4baa4b65dad1 (diff)
drm/i915: Attempt to uncouple object after catastrophic failure in unbind
If we fail to flush outstanding GPU writes but return the memory to the system, we risk corrupting memory should the GPU recovery and complete those writes. On the other hand, if we bail early and free the object then we have a definite use-after-free and real memory corruption. Choose the lesser of two evils, since in order to recover from the hung GPU we need to completely reset it, those pending writes should never happen. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Eric Anholt <eric@anholt.net>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions