Re: [PATCH] drm/ttm: fix leaking fences via ttm_buffer_object_transfer

On Wed, Feb 26, 2020 at 8:30 AM Christian König wrote: > > Am 25.02.20 um 20:12 schrieb Christian König: > > Am 25.02.20 um 20:11 schrieb Alex Deucher: > >> On Tue, Feb 25, 2020 at 2:09 PM Christian König > >> wrote: > >>> Am 25.02.20 um 19:56 schrieb Alex Deucher: > From: Ahzo > > >>>

Re: [PATCH] drm/ttm: fix leaking fences via ttm_buffer_object_transfer

On Wed, Feb 26, 2020 at 2:30 PM Christian König wrote: > > Am 25.02.20 um 20:12 schrieb Christian König: > > Am 25.02.20 um 20:11 schrieb Alex Deucher: > >> On Tue, Feb 25, 2020 at 2:09 PM Christian König > >> wrote: > >>> Am 25.02.20 um 19:56 schrieb Alex Deucher: > From: Ahzo > > >>>

Re: [PATCH] drm/ttm: fix leaking fences via ttm_buffer_object_transfer

Am 25.02.20 um 20:12 schrieb Christian König: Am 25.02.20 um 20:11 schrieb Alex Deucher: On Tue, Feb 25, 2020 at 2:09 PM Christian König wrote: Am 25.02.20 um 19:56 schrieb Alex Deucher: From: Ahzo Set the drm_device to NULL, so that the newly created buffer object doesn't appear to use the

Re: [PATCH] drm/ttm: fix leaking fences via ttm_buffer_object_transfer

Am 25.02.20 um 20:11 schrieb Alex Deucher: On Tue, Feb 25, 2020 at 2:09 PM Christian König wrote: Am 25.02.20 um 19:56 schrieb Alex Deucher: From: Ahzo Set the drm_device to NULL, so that the newly created buffer object doesn't appear to use the embedded gem object. This is necessary, becau

Re: [PATCH] drm/ttm: fix leaking fences via ttm_buffer_object_transfer

On Tue, Feb 25, 2020 at 2:09 PM Christian König wrote: > > Am 25.02.20 um 19:56 schrieb Alex Deucher: > > From: Ahzo > > > > Set the drm_device to NULL, so that the newly created buffer object > > doesn't appear to use the embedded gem object. > > > > This is necessary, because otherwise no corre

Re: [PATCH] drm/ttm: fix leaking fences via ttm_buffer_object_transfer

Am 25.02.20 um 19:56 schrieb Alex Deucher: From: Ahzo Set the drm_device to NULL, so that the newly created buffer object doesn't appear to use the embedded gem object. This is necessary, because otherwise no corresponding dma_resv_fini for the dma_resv_init is called, resulting in a memory le

[PATCH] drm/ttm: fix leaking fences via ttm_buffer_object_transfer

From: Ahzo Set the drm_device to NULL, so that the newly created buffer object doesn't appear to use the embedded gem object. This is necessary, because otherwise no corresponding dma_resv_fini for the dma_resv_init is called, resulting in a memory leak. The dma_resv_fini in ttm_bo_release_list