The patch titled Subject: zram-idle-writeback-fixes-and-cleanup-fix has been added to the -mm tree. Its filename is zram-idle-writeback-fixes-and-cleanup-fix.patch This patch should soon appear at http://ozlabs.org/~akpm/mmots/broken-out/zram-idle-writeback-fixes-and-cleanup-fix.patch and later at http://ozlabs.org/~akpm/mmotm/broken-out/zram-idle-writeback-fixes-and-cleanup-fix.patch 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 and is updated there every 3-4 working days ------------------------------------------------------ From: Minchan Kim <minchan@xxxxxxxxxx> Subject: zram-idle-writeback-fixes-and-cleanup-fix Srinivas reported to me that I missed spin_lock_init in this patch although I have that one in internal tree. Link: http://lkml.kernel.org/r/20190103001601.GA255139@xxxxxxxxxx Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/block/zram/zram_drv.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) --- a/drivers/block/zram/zram_drv.c~zram-idle-writeback-fixes-and-cleanup-fix +++ a/drivers/block/zram/zram_drv.c @@ -1907,7 +1907,9 @@ static int zram_add(void) device_id = ret; init_rwsem(&zram->init_lock); - +#ifdef CONFIG_ZRAM_WRITEBACK + spin_lock_init(&zram->wb_limit_lock); +#endif queue = blk_alloc_queue(GFP_KERNEL); if (!queue) { pr_err("Error allocating disk queue for device %d\n", _ Patches currently in -mm which might be from minchan@xxxxxxxxxx are zram-idle-writeback-fixes-and-cleanup.patch zram-idle-writeback-fixes-and-cleanup-fix.patch