fsck.ext4 -n exited with status code 12
e2fsck 1.47.0 (5-Feb-2023)
Invalid project quota inode 1.  Fix? no

syzkaller contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Quota inode is not in use, but contains data.  Clear? no

Quota inode is not in use, but contains data.  Clear? no

Inode 12 is a character device but it looks like it is really a directory.
Fix? no

Inode 12, i_blocks is 8, should be 0.  Fix? no

Extended attribute block 19 has h_blocks > 1.  Clear? no

Inode 15 has an invalid extent
	(logical block 256, invalid physical block 65535, len 1)
Clear? no

Inode 15, i_blocks is 16, should be 8.  Fix? no

Inode 16, i_size is 0, should be 12288.  Fix? no

Inode 17, i_size is 1407374883553380, should be 4096.  Fix? no


Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 2: 3
Multiply-claimed block(s) in inode 13: 3
Illegal block number passed to ext2fs_test_block_bitmap #65535 for multiply claimed block map
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 2 inodes containing multiply-claimed blocks.)

File ??? (inode #2, mod time Tue Nov 22 15:59:46 2022) 
  has 1 multiply-claimed block(s), shared with 1 file(s):
	... (inode #13, mod time Tue Nov 22 15:59:46 2022)
Clone multiply-claimed blocks? no

Delete file? no

File ... (inode #13, mod time Tue Nov 22 15:59:46 2022) 
  has 1 multiply-claimed block(s), shared with 1 file(s):
	??? (inode #2, mod time Tue Nov 22 15:59:46 2022)
Clone multiply-claimed blocks? no

Delete file? no

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

e2fsck: aborted

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