ubi: fastmap: Fix missed fm_anchor PEB in wear-leveling after disabling fastmap
authorZhihao Cheng <chengzhihao1@huawei.com>
Tue, 9 Aug 2022 07:06:19 +0000 (15:06 +0800)
committerRichard Weinberger <richard@nod.at>
Thu, 2 Feb 2023 20:13:49 +0000 (21:13 +0100)
commit76f9476ece445a07aeb72df9d896cd563fb5b50f
tree49db363ff94dbf2bf8eaba407bb880efe24d979a
parent66f4742e93523ab2f062d9d9828b3e590bc61536
ubi: fastmap: Fix missed fm_anchor PEB in wear-leveling after disabling fastmap

After disabling fastmap(ubi->fm_disabled = 1), fastmap won't be updated,
fm_anchor PEB is missed being scheduled for erasing. Besides, fm_anchor
PEB may have smallest erase count, it doesn't participate wear-leveling.
The difference of erase count between fm_anchor PEB and other PEBs will
be larger and larger later on.

In which situation fastmap can be disabled? Initially, we have an UBI
image with fastmap. Then the image will be atttached without module
parameter 'fm_autoconvert', ubi turns to full scanning mode in one
random attaching process(eg. bad fastmap caused by powercut), ubi
fastmap is disabled since then.

Fix it by not getting fm_anchor if fastmap is disabled in
ubi_refill_pools().

Fetch a reproducer in [Link].

Link: https://bugzilla.kernel.org/show_bug.cgi?id=216341
Fixes: 4b68bf9a69d22d ("ubi: Select fastmap anchor PEBs considering ...")
Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
drivers/mtd/ubi/fastmap-wl.c