On 4/24/25 11:58 AM, Chao Yu wrote:
I guess we need to figure out why f2fs_bug_on() will be tiggerred?f2fs_write_end_io() { ... f2fs_bug_on(sbi, folio->mapping == NODE_MAPPING(sbi) && folio->index != nid_of_node(&folio->page));
Well, syzkaller is very "creative" in generating weirdly damaged filesystems :-). An overall idea of the patch is that an attempt to complete I/O on a filesystem which is known to be "broken enough to run fsck" may make the things even worse (by making the filesystem even less consistent). So it may be safer just to refuse all in-flight write attempts at least. Dmitry _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
