Re: + zram-do-not-slot_free-written-back-slots.patch added to mm-hotfixes-unstable branch

[Sergey Senozhatsky <senozhatsky@chromium.org>]

On (26/03/19 15:44), Andrew Morton wrote:
> The patch titled
>      Subject: zram: do not slot_free() written-back slots
> has been added to the -mm mm-hotfixes-unstable branch.  Its filename is
>      zram-do-not-slot_free-written-back-slots.patch
> 
> This patch will shortly appear at
>      https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/zram-do-not-slot_free-written-back-slots.patch
> 
> This patch will later appear in the mm-hotfixes-unstable branch at
>     git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> 
> Before you just go and hit "reply", please:
>    a) Consider who else should be cc'ed
>    b) Prefer to cc a suitable mailing list as well
>    c) Ideally: find the original patch on the mailing list and do a
>       reply-to-all to that, adding suitable additional cc's
> 
> *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
> 
> The -mm tree is included into linux-next via various
> branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> and is updated there most days
> 
> ------------------------------------------------------
> From: Sergey Senozhatsky <senozhatsky@chromium.org>
> Subject: zram: do not slot_free() written-back slots
> Date: Thu, 19 Mar 2026 12:44:56 +0900
> 
> slot_free() basically completely resets the slots by clearing all of its
> flags and attributes.  While zram_writeback_complete() restores some of
> flags back (those that are necessary for async read decompression) we
> still lose a lot of slot's metadata.  For example, slot's ac-time, or
> ZRAM_INCOMPRESSIBLE.
> 
> Do not slot_free() on writeback, instead clear only those flags/attrs that
> we need to clear.

Hello Andrew,
I just sent a v2 with updated commit message [1]

[1] https://lore.kernel.org/linux-mm/20260320023143.2372879-1-senozhatsky@chromium.org