[v6.6] WARNING in ext4_dirty_folio

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: af1544b5d072 Linux 6.6.107
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=156dd0e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=63515cf575687a69e6b5
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=169f6712580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/70417990f48e/disk-af1544b5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1513b6e63f4f/vmlinux-af1544b5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5648a8356789/bzImage-af1544b5.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/c496482662cf/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=17587c7c580000)

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 11379 at fs/ext4/inode.c:3583 ext4_dirty_folio+0x159/0x310 fs/ext4/inode.c:3583
Modules linked in:
CPU: 0 PID: 11379 Comm: syz.9.134 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:ext4_dirty_folio+0x159/0x310 fs/ext4/inode.c:3583
Code: 49 83 3f 00 74 1f e8 56 91 53 ff 48 8b 3c 24 48 89 de 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 8c 85 c9 ff e8 37 91 53 ff <0f> 0b eb dd e8 2e 91 53 ff 0f 0b eb af e8 25 91 53 ff 48 89 df 48
RSP: 0018:ffffc90004ce7998 EFLAGS: 00010293
RAX: ffffffff82320669 RBX: ffffea0001b566c0 RCX: ffff88807bb00000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 1ffffd400036acd8 R08: ffffea0001b566c7 R09: 1ffffd400036acd8
R10: dffffc0000000000 R11: fffff9400036acd9 R12: dffffc0000000000
R13: 1ffffd400036acd9 R14: 0000000000000001 R15: ffffea0001b566e8
FS: 00007ff0f49676c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000002d126000 CR4: 00000000003506f0
Call Trace:
<TASK>
set_page_dirty_lock+0xfc/0x2c0 mm/page-writeback.c:2825
fuse_copy_finish+0x104/0x200 fs/fuse/dev.c:678
fuse_dev_do_read+0xc44/0x11a0 fs/fuse/dev.c:1302
fuse_dev_read+0x14d/0x1d0 fs/fuse/dev.c:1367
call_read_iter include/linux/fs.h:2012 [inline]
new_sync_read fs/read_write.c:389 [inline]
vfs_read+0x431/0x920 fs/read_write.c:470
ksys_read+0x147/0x250 fs/read_write.c:613
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff0f3b8ec29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff0f4967038 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007ff0f3dd6180 RCX: 00007ff0f3b8ec29
RDX: 0000000000002020 RSI: 00002000000093c0 RDI: 0000000000000007
RBP: 00007ff0f3c11e41 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff0f3dd6218 R14: 00007ff0f3dd6180 R15: 00007ffdce3a8648
</TASK>


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup