[Intel-gfx] [PATCH] drm/core: Do not call drm_framebuffer_remove internally during teardown.

On Wed, Sep 09, 2015 at 04:33:33PM +0200, Maarten Lankhorst wrote: > Op 09-09-15 om 13:59 schreef Daniel Vetter: > > On Wed, Sep 9, 2015 at 1:51 PM, Ville Syrjälä > > wrote: > >> On Wed, Sep 09, 2015 at 01:46:21PM +0200, Maarten Lankhorst wrote: > >>> This may cause issues because encoders are a

[Intel-gfx] [PATCH] drm/core: Do not call drm_framebuffer_remove internally during teardown.

Op 09-09-15 om 13:59 schreef Daniel Vetter: > On Wed, Sep 9, 2015 at 1:51 PM, Ville Syrjälä > wrote: >> On Wed, Sep 09, 2015 at 01:46:21PM +0200, Maarten Lankhorst wrote: >>> This may cause issues because encoders are already destroyed so removing >>> active primaries may use freed memory. Inste

[Intel-gfx] [PATCH] drm/core: Do not call drm_framebuffer_remove internally during teardown.

On Wed, Sep 09, 2015 at 01:46:21PM +0200, Maarten Lankhorst wrote: > This may cause issues because encoders are already destroyed so removing > active primaries may use freed memory. Instead free the fb directly, > ignoring refcount. So what about fixing the cause, not the symptom? That is remove

[Intel-gfx] [PATCH] drm/core: Do not call drm_framebuffer_remove internally during teardown.

On Wed, Sep 9, 2015 at 1:51 PM, Ville Syrjälä wrote: > On Wed, Sep 09, 2015 at 01:46:21PM +0200, Maarten Lankhorst wrote: >> This may cause issues because encoders are already destroyed so removing >> active primaries may use freed memory. Instead free the fb directly, >> ignoring refcount. > >

[PATCH] drm/core: Do not call drm_framebuffer_remove internally during teardown.

This may cause issues because encoders are already destroyed so removing active primaries may use freed memory. Instead free the fb directly, ignoring refcount. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/drm_crtc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dri