Forgive my stubbornness, I think this strict check is good, could you show me a process to trigger this WARN_ON, it would be nice to provide a reproducer.ubi_wl_init() is called in both cases, with and without fastmap.I agree.
And ai->fastmap contains all anchor PEBs that scan_fast() found.Is it exists a case that outdated fastmap PEBs are neither counted into
This can be the most recent but also outdated anchor PEBs.
'fmhdr->erase_peb_count' nor scanned into 'ai->fastmap' after attaching
by fastmap.
[...]
I think UBI attaches failed by fastmap if kernel goes here.
1870 err = erase_aeb(ubi, aeb, sync);
Hmm, I think the paranoia check in fastmap.c is too strict these days.
if (WARN_ON(count_fastmap_pebs(ai) != ubi->peb_count -
ai->bad_peb_count - fm->used_blocks))
goto fail_bad;
It does not account ai->fastmap. So if ai->fastmap contains old anchor PEBs
this check will trigger and force falling back to scanning mode.
With this check fixed, ubi_wl_init() will erase all old PEBs from ai->fastmap.
simulate some of them on nandsim), in theory, I think the WARN_ON check is okay and all outdated fastmap PEBs can be erased in next attaching:
So I agree that this code path is wonky and can be cleaned up. But please be
extremely careful and give all your changes excessive testing with real workload
and power-cuts.Let's list all power-cut cases during fastmap updateing(I tried to