On Fri, May 27, 2022 at 05:10:43PM +0800, yebin wrote: > > Maybe you can run syzkaller with log as follows : Oh, so this was something that was found using Syzkaller. Was this using the public syzkaller; if so, can you provide a link the Syzkaller report? If this was a from privately run syzkaller instance, was there a C reproducer? It appears that this was from a fuzzed instance, and it's painful enoguh to extract the file system image from the C reproducer. I have no idea how to extract the file system image from a Syzkaller reproducer. In any case, it sounds like this was triggered from a maliciously corrupted / fuzzed image. Can this warning be triggered from a consistent file system, or does it require a corrupted extent tree? - Ted
