syzbot suspects this issue was fixed by commit:
commit 76ca4a07659a31cc62977664bcf638d6a24af068
Author: Daeho Jeong
Date: Thu Apr 28 18:18:09 2022 +
BACKPORT: f2fs: change the current atomic write way
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11287ba5e8
start
We will encounter below inconsistent status when FAULT_BLKADDR type
fault injection is on.
Info: checkpoint state = d6 : nat_bits crc fsck compacted_summary
orphan_inodes sudden-power-off
[ASSERT] (fsck_chk_inode_blk:1254) --> ino: 0x1c100 has i_blocks: 00c0,
but has 191 blocks
[FIX]
There is a potentail deadloop issue in the corner case of
CONFIG_F2FS_FAULT_INJECTION is enabled and the return value
of f2fs_reserve_new_block is error but not -ENOSPC, such as
this error case:
if (unlikely(is_inode_flag_set(dn->inode, FI_NO_ALLOC)))
return -EPERM;
besides, the
