summaryrefslogtreecommitdiff
path: root/mm/Kconfig
diff options
context:
space:
mode:
authorSergey Senozhatsky <senozhatsky@chromium.org>2022-08-24 12:51:00 +0900
committerAndrew Morton <akpm@linux-foundation.org>2022-09-11 20:26:00 -0700
commit6d2453c3dbc5f70eafc1c866289a90a1fc57ce18 (patch)
treeb71c57fa8ff8f75883c1597e31055cfa46b7ed01 /mm/Kconfig
parent67e139b02d99496c03bf3b51abad685ab3b49138 (diff)
downloadlwn-6d2453c3dbc5f70eafc1c866289a90a1fc57ce18.tar.gz
lwn-6d2453c3dbc5f70eafc1c866289a90a1fc57ce18.zip
drivers/block/zram/zram_drv.c: do not keep dangling zcomp pointer after zram reset
We do all reset operations under write lock, so we don't need to save ->disksize and ->comp to stack variables. Another thing is that ->comp is freed during zram reset, but comp pointer is not NULL-ed, so zram keeps the freed pointer value. Link: https://lkml.kernel.org/r/20220824035100.971816-1-senozhatsky@chromium.org Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org> Cc: Minchan Kim <minchan@kernel.org> Cc: Nitin Gupta <ngupta@vflare.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/Kconfig')
0 files changed, 0 insertions, 0 deletions