fsck.ext4 -n exited with status code 12
e2fsck 1.47.0 (5-Feb-2023)
One or more block group descriptor checksums are invalid.  Fix? no

Group descriptor 0 checksum is 0x8245, should be 0x4287.  IGNORED.
syzkaller contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
HTREE directory inode 2 has an invalid root node.
Clear HTree index? no

Inode 2, i_size is 262144, should be 1024.  Fix? no

Inode 15 has INLINE_DATA_FL flag but extended attribute not found.  Truncate? no

Inode 15 extended attribute is corrupt (allocation collision).  Clear? no

Inode 17 has INLINE_DATA_FL flag but extended attribute not found.  Truncate? no

Inode 11 block 12 conflicts with critical metadata, skipping block checks.
Inode 11 block 2 conflicts with critical metadata, skipping block checks.
Inode 11 block 3 conflicts with critical metadata, skipping block checks.
Inode 11 block 7 conflicts with critical metadata, skipping block checks.
Inode 11 block 4 conflicts with critical metadata, skipping block checks.
Inode 11 block 5 conflicts with critical metadata, skipping block checks.
Inode 11 block 2 conflicts with critical metadata, skipping block checks.
Inode 11 block 5 conflicts with critical metadata, skipping block checks.
Inode 11 block 5 conflicts with critical metadata, skipping block checks.
Too many illegal blocks in inode 11.
Clear inode? no

Suppress messages? no

Inode 11 has illegal block(s).  Clear? no

Illegal block #221453 (1024) in inode 11.  IGNORED.
Illegal block #221458 (32512) in inode 11.  IGNORED.
Inode 11, i_size is 10, should be 226775040.  Fix? no

Inode 11, i_blocks is 22, should be 114.  Fix? no

Inode 13 has illegal block(s).  Clear? no

Illegal double indirect block (33619980) in inode 13.  IGNORED.
Error while iterating over blocks in inode 13: Illegal doubly indirect block found

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

e2fsck: aborted

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