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
Extended attribute in inode 15 has a hash (2538838903) which is invalid
Clear? no

Inode 15 logical block 6 (physical block 2) violates cluster allocation rules.
Will fix in pass 1B.
Inode 15, i_size is 10, should be 7168.  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


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 15: 2
Illegal block number passed to ext2fs_test_block_bitmap #1342177290 for multiply claimed block map
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 1 inodes containing multiply-claimed blocks.)

File /file1 (inode #15, mod time Tue Nov 22 15:59:52 2022) 
  has 1 multiply-claimed block(s), shared with 1 file(s):
	<filesystem metadata>
Clone multiply-claimed blocks? no

Delete file? 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 **********