Patch "drm/ttm: Fix an invalid freeing on already freed page in error path" has been added to the 6.1-stable tree

2024-02-26 Thread gregkh
This is a note to let you know that I've just added the patch titled drm/ttm: Fix an invalid freeing on already freed page in error path to the 6.1-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the

Patch "drm/ttm: Fix an invalid freeing on already freed page in error path" has been added to the 6.6-stable tree

2024-02-26 Thread gregkh
This is a note to let you know that I've just added the patch titled drm/ttm: Fix an invalid freeing on already freed page in error path to the 6.6-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the

Patch "drm/ttm: Fix an invalid freeing on already freed page in error path" has been added to the 6.7-stable tree

2024-02-26 Thread gregkh
This is a note to let you know that I've just added the patch titled drm/ttm: Fix an invalid freeing on already freed page in error path to the 6.7-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the

Patch "drm/ttm: Fix an invalid freeing on already freed page in error path" has been added to the 5.15-stable tree

2024-02-26 Thread gregkh
This is a note to let you know that I've just added the patch titled drm/ttm: Fix an invalid freeing on already freed page in error path to the 5.15-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the

Re: [PATCH] drm/ttm: Fix an invalid freeing on already freed page in error path

2024-02-22 Thread Christian König
Am 22.02.24 um 08:34 schrieb Thomas Hellström: On Wed, 2024-02-21 at 11:26 +0100, Christian König wrote: Am 21.02.24 um 08:33 schrieb Thomas Hellström: If caching mode change fails due to, for example, OOM we free the allocated pages in a two-step process. First the pages for which the caching

Re: [PATCH] drm/ttm: Fix an invalid freeing on already freed page in error path

2024-02-22 Thread Thomas Hellström
On Thu, 2024-02-22 at 08:34 +0100, Thomas Hellström wrote: > On Wed, 2024-02-21 at 11:26 +0100, Christian König wrote: > > Am 21.02.24 um 08:33 schrieb Thomas Hellström: > > > If caching mode change fails due to, for example, OOM we > > > free the allocated pages in a two-step process. First the

Re: [PATCH] drm/ttm: Fix an invalid freeing on already freed page in error path

2024-02-21 Thread Thomas Hellström
On Wed, 2024-02-21 at 11:26 +0100, Christian König wrote: > Am 21.02.24 um 08:33 schrieb Thomas Hellström: > > If caching mode change fails due to, for example, OOM we > > free the allocated pages in a two-step process. First the pages > > for which the caching change has already succeeded.

Re: [PATCH] drm/ttm: Fix an invalid freeing on already freed page in error path

2024-02-21 Thread Christian König
Am 21.02.24 um 08:33 schrieb Thomas Hellström: If caching mode change fails due to, for example, OOM we free the allocated pages in a two-step process. First the pages for which the caching change has already succeeded. Secondly the pages for which a caching change did not succeed. However the

Re: [PATCH] drm/ttm: Fix an invalid freeing on already freed page in error path

2024-02-21 Thread Matthew Auld
On 21/02/2024 07:33, Thomas Hellström wrote: If caching mode change fails due to, for example, OOM we free the allocated pages in a two-step process. First the pages for which the caching change has already succeeded. Secondly the pages for which a caching change did not succeed. However the

[PATCH] drm/ttm: Fix an invalid freeing on already freed page in error path

2024-02-20 Thread Thomas Hellström
If caching mode change fails due to, for example, OOM we free the allocated pages in a two-step process. First the pages for which the caching change has already succeeded. Secondly the pages for which a caching change did not succeed. However the second step was incorrectly freeing the pages