]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
zram: check comp is non-NULL before calling comp_destroy
authorDominique Martinet <dominique.martinet@atmark-techno.com>
Tue, 7 Jan 2025 07:16:04 +0000 (16:16 +0900)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 9 Jan 2025 12:30:07 +0000 (13:30 +0100)
commit677294e4da96547b9ea2955661a4bbf1d13552a3
tree83d4b070c6ce13a472f460bde84ddb9d7e8c018d
parent91b493f15d65266ebba806553c97a2ae5df581ce
zram: check comp is non-NULL before calling comp_destroy

This is a pre-requisite for the backport of commit 74363ec674cb ("zram:
fix uninitialized ZRAM not releasing backing device"), which has been
implemented differently in commit 7ac07a26dea7 ("zram: preparation for
multi-zcomp support") upstream.

We only need to ensure that zcomp_destroy is not called with a NULL
comp, so add this check as the other commit cannot be backported easily.

Stable-dep-of: 74363ec674cb ("zram: fix uninitialized ZRAM not releasing backing device")
Link: https://lore.kernel.org/Z3ytcILx4S1v_ueJ@codewreck.org
Suggested-by: Kairui Song <kasong@tencent.com>
Signed-off-by: Dominique Martinet <dominique.martinet@atmark-techno.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/block/zram/zram_drv.c