fsck.ext4 -n exited with status code 12
e2fsck 1.47.0 (5-Feb-2023)
syzkaller contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 15 has extent header but inline data flag is set.
Fix? no

Inode 15 seems to have inline data but extent flag is set.
Fix? no

Inode 15 has inline data and extent flags set but i_block contains junk.
Clear inode? no

Inode 15 has INLINE_DATA_FL flag on filesystem without inline data support.
Clear? no

Extended attribute in inode 15 has a hash (2538838903) which is invalid
Clear? no

Inode 15, i_blocks is 64, should be 32.  Fix? no

Inode 17 has an invalid extent
	(logical block 0, invalid physical block 21474836640, len 1)
Clear? no

Inode 17, i_size is 504403158265561087, should be 0.  Fix? no

Inode 17, i_blocks is 32, should be 0.  Fix? no

Pass 2: Checking directory structure
Directory inode 2, block #0, offset 876: directory corrupted
Salvage? no

e2fsck: aborted

syzkaller: ********** WARNING: Filesystem still has errors **********