It was possible for invalidate range start mmu notifier callback to race
with releasing userptr object. If the object is released prior to
taking a spinlock in the callback, we'll encounter a null pointer
dereference.
Cc: Chris Wilson ch...@chris-wilson.co.uk
Signed-off-by: Michał Winiarski
On Tue, Feb 03, 2015 at 03:39:17PM +0100, Michał Winiarski wrote:
It was possible for invalidate range start mmu notifier callback to race
with releasing userptr object. If the object is released prior to
taking a spinlock in the callback, we'll encounter a null pointer
dereference.
Cc:
On Tue, Feb 03, 2015 at 03:01:38PM +, Chris Wilson wrote:
On Tue, Feb 03, 2015 at 03:39:17PM +0100, Michał Winiarski wrote:
It was possible for invalidate range start mmu notifier callback to race
with releasing userptr object. If the object is released prior to
taking a spinlock in the
