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 16 logical block 2 (physical block 96) violates cluster allocation rules.
Will fix in pass 1B.
Inode 16 logical block 3 (physical block 97) violates cluster allocation rules.
Will fix in pass 1B.
Inode 16 logical block 4 (physical block 98) violates cluster allocation rules.
Will fix in pass 1B.
Inode 16 logical block 5 (physical block 99) violates cluster allocation rules.
Will fix in pass 1B.
Inode 16 logical block 6 (physical block 100) violates cluster allocation rules.
Will fix in pass 1B.
Inode 16, i_size is 8796093031208, should be 14336.  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 16: 96--100
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 /file2 (inode #16, mod time Tue Nov 22 15:59:50 2022) 
  has 1 multiply-claimed block(s), shared with 0 file(s):
Clone multiply-claimed blocks? no

Delete file? no

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

e2fsck: aborted

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