[ext4?] kernel BUG in corrupted

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3949d1610004 Linux 4.14.304
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13fda715480000
kernel config: https://syzkaller.appspot.com/x/.config?x=db4418ccbf710113
dashboard link: https://syzkaller.appspot.com/bug?extid=33c1b672f1097cc83aa9
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1437a8d1480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11b770c9480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2230a6d7e7f4/disk-3949d161.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9b8d5667f298/vmlinux-3949d161.xz
kernel image: https://storage.googleapis.com/syzbot-assets/825468a3e783/bzImage-3949d161.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e319539d3d43/mount_0.gz

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

------------[ cut here ]------------
------------[ cut here ]------------
kernel BUG at fs/ext4/inode.c:2861!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
WARNING: CPU: 1 PID: 22698 at fs/ext4/inode.c:3930 ext4_set_page_dirty+0xd3/0x130 fs/ext4/inode.c:3930
Modules linked in:
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 22663 Comm: syz-executor333 Not tainted 4.14.304-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
task: ffff88809b880040 task.stack: ffff888098488000
RIP: 0010:ext4_writepages+0x27fc/0x32a0 fs/ext4/inode.c:2861
RSP: 0018:ffff88809848f638 EFLAGS: 00010297
RAX: ffff88809b880040 RBX: 00000000a802c010 RCX: 1ffff11013710209
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: ffff88809b881048
RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000005050f
R10: ffff88809b880918 R11: ffff88809b880040 R12: 0000000000000001
R13: dffffc0000000000 R14: ffff88808ae685f0 R15: ffff88809848fa60
FS: 00007f95b83d8700(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000100 CR3: 00000000a2f19000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_writepages+0xc3/0x240 mm/page-writeback.c:2361
__filemap_fdatawrite_range+0x236/0x310 mm/filemap.c:346
file_write_and_wait_range+0x86/0xd0 mm/filemap.c:678
__generic_file_fsync+0x70/0x190 fs/libfs.c:1001
ext4_sync_file+0x8ed/0x12c0 fs/ext4/fsync.c:118
vfs_fsync_range+0x103/0x260 fs/sync.c:196
generic_write_sync include/linux/fs.h:2684 [inline]
ext4_file_write_iter+0x5fa/0xd20 fs/ext4/file.c:281
call_write_iter include/linux/fs.h:1780 [inline]
new_sync_write fs/read_write.c:469 [inline]
__vfs_write+0x44c/0x630 fs/read_write.c:482
vfs_write+0x17f/0x4d0 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7f95b8c3abe9
RSP: 002b:00007f95b83d8208 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f95b8cc0588 RCX: 00007f95b8c3abe9
RDX: 0000000000000014 RSI: 0000000020000100 RDI: 0000000000000008
RBP: 00007f95b8cc0580 R08: 0000000000000000 R09: 00007f95b8cc0588
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f95b8cc058c
R13: 00007ffd89d04bef R14: 00007f95b83d8300 R15: 0000000000022000
Code: ff ff 4c 89 ff e8 f5 b2 c3 ff e9 98 db ff ff e8 2b f0 99 ff 48 8b bc 24 b8 00 00 00 e8 be 58 b1 ff e9 18 f5 ff ff e8 14 f0 99 ff <0f> 0b e8 0d f0 99 ff 48 8b bc 24 b8 00 00 00 e8 a0 58 b1 ff 8b
RIP: ext4_writepages+0x27fc/0x32a0 fs/ext4/inode.c:2861 RSP: ffff88809848f638
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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