diff options
author | 2015-02-03 15:48:17 +0100 | |
---|---|---|
committer | 2015-02-05 16:31:30 +0200 | |
commit | 460822b0b1a77db859b0320469799fa4dbe4d367 (patch) | |
tree | 3f2e09686dc7e70d82a75c4d475e84f944606ebe /tools/perf/scripts/python/export-to-postgresql.py | |
parent | drm/i915: Update DRIVER_DATE to 20150130 (diff) | |
download | wireguard-linux-460822b0b1a77db859b0320469799fa4dbe4d367.tar.xz wireguard-linux-460822b0b1a77db859b0320469799fa4dbe4d367.zip |
drm/i915: Prevent use-after-free in invalidate_range_start callback
It's possible for invalidate_range_start mmu notifier callback to race
against userptr object release. If the gem object was released prior to
obtaining the spinlock in invalidate_range_start we're hitting null
pointer dereference.
Testcase: igt/gem_userptr_blits/stress-mm-invalidate-close
Testcase: igt/gem_userptr_blits/stress-mm-invalidate-close-overlap
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: stable@vger.kernel.org
[Jani: added code comment suggested by Chris]
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions