On Mon, Jul 09, 2018 at 02:42:01PM +0800, Qu Wenruo wrote: > Can be fetched with all existing tree-checker/bg<->chunk error detector > from github: > https://github.com/adam900710/linux/tree/tree_checker_enhance > > Still some fuzzed images reported from Xu Wen. > This time, 2 can be fixed by chunk <-> dev extent mapping verification. > One BUG_ON() can be removed. > > The remaining 2 images are all mostly about extent tree corruption, > which is not as easy to detect, since extent tree has way more complex > reference relationship. > > At least, fix what we can first. > > And for chunk <-> dev extent mapping verification, it will trigger > read on the whole device tree, to iterate through all DEV_EXTENT items. > This will introduce an extra overhead on mount. > > However since device tree is pretty small (the same level as chunk tree), > and according to previous analyse on mount time, chunk tree iteration is > only a pretty small fraction of the whole mount time (less than 5%), it > shouldn't bring obvious impact to users.
Ok, that's acceptable. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
