diff options
author | Zhihao Cheng <chengzhihao1@huawei.com> | 2020-07-07 21:41:00 +0800 |
---|---|---|
committer | Richard Weinberger <richard@nod.at> | 2020-08-02 23:56:13 +0200 |
commit | 3b185255bb2f34fa6927619b9ef27f192a3d9f5a (patch) | |
tree | 80bdf908124243d22548080f619d146461aac55b /drivers/mtd/ubi | |
parent | fcf44196305788b173748356a4f3ac2630454ba0 (diff) | |
download | linux-stable-3b185255bb2f34fa6927619b9ef27f192a3d9f5a.tar.gz linux-stable-3b185255bb2f34fa6927619b9ef27f192a3d9f5a.tar.bz2 linux-stable-3b185255bb2f34fa6927619b9ef27f192a3d9f5a.zip |
ubi: fastmap: Don't produce the initial next anchor PEB when fastmap is disabled
Following process triggers a memleak caused by forgetting to release the
initial next anchor PEB (CONFIG_MTD_UBI_FASTMAP is disabled):
1. attach -> __erase_worker -> produce the initial next anchor PEB
2. detach -> ubi_fastmap_close (Do nothing, it should have released the
initial next anchor PEB)
Don't produce the initial next anchor PEB in __erase_worker() when fastmap
is disabled.
Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
Suggested-by: Sascha Hauer <s.hauer@pengutronix.de>
Fixes: f9c34bb529975fe ("ubi: Fix producing anchor PEBs")
Reported-by: syzbot+d9aab50b1154e3d163f5@syzkaller.appspotmail.com
Signed-off-by: Richard Weinberger <richard@nod.at>
Diffstat (limited to 'drivers/mtd/ubi')
-rw-r--r-- | drivers/mtd/ubi/wl.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/mtd/ubi/wl.c b/drivers/mtd/ubi/wl.c index 27636063ed1b..42cac572f82d 100644 --- a/drivers/mtd/ubi/wl.c +++ b/drivers/mtd/ubi/wl.c @@ -1086,7 +1086,8 @@ static int __erase_worker(struct ubi_device *ubi, struct ubi_work *wl_wrk) if (!err) { spin_lock(&ubi->wl_lock); - if (!ubi->fm_next_anchor && e->pnum < UBI_FM_MAX_START) { + if (!ubi->fm_disabled && !ubi->fm_next_anchor && + e->pnum < UBI_FM_MAX_START) { /* Abort anchor production, if needed it will be * enabled again in the wear leveling started below. */ |