[PATCH] ttm: on move memory failure don't leave a node dangling

2013-01-16 Thread Dave Airlie
if we have a move notify callback, when moving fails, we call move notify the opposite way around, however this ends up with *mem containing the mm_node from the bo, which means we double free it. This is a follow on to the previous fix. Signed-off-by: Dave Airlie --- drivers/gpu/drm/ttm/ttm_bo.

[PATCH] ttm: on move memory failure don't leave a node dangling

2013-01-16 Thread Jerome Glisse
On Wed, Jan 16, 2013 at 1:01 AM, Dave Airlie wrote: > if we have a move notify callback, when moving fails, we call move notify > the opposite way around, however this ends up with *mem containing the mm_node > from the bo, which means we double free it. This is a follow on to the > previous > fi

Re: [PATCH] ttm: on move memory failure don't leave a node dangling

2013-01-16 Thread Jerome Glisse
On Wed, Jan 16, 2013 at 1:01 AM, Dave Airlie wrote: > if we have a move notify callback, when moving fails, we call move notify > the opposite way around, however this ends up with *mem containing the mm_node > from the bo, which means we double free it. This is a follow on to the > previous > fi

[PATCH] ttm: on move memory failure don't leave a node dangling

2013-01-15 Thread Dave Airlie
if we have a move notify callback, when moving fails, we call move notify the opposite way around, however this ends up with *mem containing the mm_node from the bo, which means we double free it. This is a follow on to the previous fix. Signed-off-by: Dave Airlie --- drivers/gpu/drm/ttm/ttm_bo.