kernel BUG in ext4_writepages (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 673a7341bdab Merge 5.10.153 into android12-5.10-lts
git tree: android12-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=13b91573880000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e4b21ca1ff54f91
dashboard link: https://syzkaller.appspot.com/bug?extid=611768e51a769a957b02
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c2e53d880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=101e0755880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/783883aa563c/disk-673a7341.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2dba445780bf/vmlinux-673a7341.xz
kernel image: https://storage.googleapis.com/syzbot-assets/879a2fd72143/bzImage-673a7341.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/7a004951c719/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+611768...@syzkaller.appspotmail.com

block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters
------------[ cut here ]------------
kernel BUG at fs/ext4/inode.c:2767!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 372 Comm: syz-executor227 Not tainted 5.10.153-syzkaller-00570-g673a7341bdab #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:ext4_writepages+0x36f6/0x3710 fs/ext4/inode.c:2766
Code: c6 31 ff e8 3c ec 8f ff 84 db 75 2c e8 23 e9 8f ff 48 bb 00 00 00 00 00 fc ff df 4c 8b 64 24 40 e9 28 f7 ff ff e8 0a e9 8f ff <0f> 0b e8 03 e9 8f ff e8 8d 87 23 ff eb a0 e8 f7 e8 8f ff e8 81 87
RSP: 0018:ffffc90000b87300 EFLAGS: 00010293
RAX: ffffffff81dcfab6 RBX: 0000008000000000 RCX: ffff888106583b40
RDX: 0000000000000000 RSI: 0000008000000000 RDI: 0000000000000000
RBP: ffffc90000b876f0 R08: ffffffff81dcca9a R09: ffffed1021ce176d
R10: ffffed1021ce176d R11: 1ffff11021ce176c R12: ffff8881059d4000
R13: ffffc90000b875c0 R14: 0000008410000000 R15: ffffc90000b87860
FS: 00007f038e0a9700(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000f82 CR3: 0000000106388000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_writepages+0x13a/0x280 mm/page-writeback.c:2358
__filemap_fdatawrite_range+0x354/0x420 mm/filemap.c:427
file_write_and_wait_range+0x89/0x120 mm/filemap.c:766
ext4_sync_file+0x19e/0x9d0 fs/ext4/fsync.c:151
vfs_fsync_range+0x17b/0x190 fs/sync.c:202
generic_write_sync include/linux/fs.h:2801 [inline]
ext4_buffered_write_iter+0x565/0x610 fs/ext4/file.c:280
ext4_file_write_iter+0x192/0x1c70 fs/ext4/file.c:689
call_write_iter include/linux/fs.h:1952 [inline]
new_sync_write fs/read_write.c:518 [inline]
vfs_write+0xc4a/0xf80 fs/read_write.c:605
ksys_write+0x198/0x2c0 fs/read_write.c:658
__do_sys_write fs/read_write.c:670 [inline]
__se_sys_write fs/read_write.c:667 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:667
do_syscall_64+0x34/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7f038e0fc889
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 14 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f038e0a9208 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f038e1816e8 RCX: 00007f038e0fc889
RDX: 0000000000000009 RSI: 0000000020000f80 RDI: 0000000000000004
RBP: 00007f038e1816e0 R08: 00007f038e1816e0 R09: 0000000000000000
R10: 00007f038e0a9210 R11: 0000000000000246 R12: 00007f038e1816ec
R13: 00007ffdf7fe3e4f R14: 00007f038e0a9300 R15: 0000000000022000
Modules linked in:
---[ end trace 692ed9bbd04ade5c ]---
RIP: 0010:ext4_writepages+0x36f6/0x3710 fs/ext4/inode.c:2766
Code: c6 31 ff e8 3c ec 8f ff 84 db 75 2c e8 23 e9 8f ff 48 bb 00 00 00 00 00 fc ff df 4c 8b 64 24 40 e9 28 f7 ff ff e8 0a e9 8f ff <0f> 0b e8 03 e9 8f ff e8 8d 87 23 ff eb a0 e8 f7 e8 8f ff e8 81 87
RSP: 0018:ffffc90000b87300 EFLAGS: 00010293
RAX: ffffffff81dcfab6 RBX: 0000008000000000 RCX: ffff888106583b40
RDX: 0000000000000000 RSI: 0000008000000000 RDI: 0000000000000000
RBP: ffffc90000b876f0 R08: ffffffff81dcca9a R09: ffffed1021ce176d
R10: ffffed1021ce176d R11: 1ffff11021ce176c R12: ffff8881059d4000
R13: ffffc90000b875c0 R14: 0000008410000000 R15: ffffc90000b87860
FS: 00007f038e0a9700(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000f82 CR3: 0000000106388000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches