fsck.ext4 -n exited with status code 4
e2fsck 1.47.0 (5-Feb-2023)
syzkaller contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 11 has an invalid extent
	(logical block 0, invalid physical block 369098784, len 7)
Clear? no

Inode 11 is a zero-length directory.  Clear? no

Inode 11, i_size is 14336, should be 0.  Fix? no

Inode 11, i_blocks is 64, should be 0.  Fix? no

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

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

Inode 12, i_size is 60, should be 0.  Fix? no

Inode 16, i_blocks is 7, should be 64.  Fix? no

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
'..' in /lost+found (11) is <The NULL inode> (0), should be / (2).
Fix? no

'..' in /file0 (12) is <The NULL inode> (0), should be / (2).
Fix? no

Pass 4: Checking reference counts
Inode 2 ref count is 4, should be 2.  Fix? no

Inode 11 ref count is 2, should be 1.  Fix? no

Inode 12 ref count is 2, should be 1.  Fix? no

Unattached inode 13
Connect to /lost+found? no

Unattached inode 14
Connect to /lost+found? no

Pass 5: Checking group summary information
Block bitmap differences:  -32
Fix? no

Free blocks count wrong for group #0 (150994969, counted=25).
Fix? no


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

syzkaller: 17/32 files (0.0% non-contiguous), 112/512 blocks