diff options
| author | Kairui Song <kasong@tencent.com> | 2024-12-10 00:57:16 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-12-27 14:02:13 +0100 |
| commit | 6fb92e9a52e3feae309a213950f21dfcd1eb0b40 (patch) | |
| tree | 55a586fa931b07871360e49418db62cc4352192c /mm | |
| parent | 6d91e90cfc34409bfb619ca43eb24559f767262e (diff) | |
| download | linux-6fb92e9a52e3feae309a213950f21dfcd1eb0b40.tar.gz linux-6fb92e9a52e3feae309a213950f21dfcd1eb0b40.tar.bz2 linux-6fb92e9a52e3feae309a213950f21dfcd1eb0b40.zip | |
zram: fix uninitialized ZRAM not releasing backing device
commit 74363ec674cb172d8856de25776c8f3103f05e2f upstream.
Setting backing device is done before ZRAM initialization. If we set the
backing device, then remove the ZRAM module without initializing the
device, the backing device reference will be leaked and the device will be
hold forever.
Fix this by always reset the ZRAM fully on rmmod or reset store.
Link: https://lkml.kernel.org/r/20241209165717.94215-3-ryncsn@gmail.com
Fixes: 013bf95a83ec ("zram: add interface to specif backing device")
Signed-off-by: Kairui Song <kasong@tencent.com>
Reported-by: Desheng Wu <deshengwu@tencent.com>
Suggested-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions