[syzbot] [block?] kernel BUG in folio_unmap_invalidate

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a59f57e2aa12 Merge tag 'watchdog-for-v7.2-rc7' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13196fb9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=158601bb8cb292dd
dashboard link: https://syzkaller.appspot.com/bug?extid=c393fb3e3a7a1bfa5927
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/52f4874481e5/disk-a59f57e2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bb5cb2b16c65/vmlinux-a59f57e2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e5cc16a680f1/bzImage-a59f57e2.xz

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

------------[ cut here ]------------
kernel BUG at mm/truncate.c:632!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 13095 Comm: syz.4.2094 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:folio_unmap_invalidate+0x7ee/0x830 mm/truncate.c:632
Code: c6 c0 71 78 8b e8 a2 e9 1d ff 90 0f 0b e8 3a f4 bb ff 48 89 df 48 c7 c6 c0 71 78 8b e8 8b e9 1d ff 90 0f 0b e8 23 f4 bb ff 90 <0f> 0b e8 1b f4 bb ff 48 89 df 48 c7 c6 c0 71 78 8b e8 6c e9 1d ff
RSP: 0018:ffffc900064a7830 EFLAGS: 00010287
RAX: ffffffff8209d53d RBX: ffffea0000b443c0 RCX: 0000000000080000
RDX: ffffc90013401000 RSI: 0000000000038e38 RDI: 0000000000038e39
RBP: ffffea0000b443c8 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff9400016887f R12: 0000000000000001
R13: dffffc0000000000 R14: 1ffffd4000168879 R15: 1ffffd4000168878
FS: 00007f0ec44146c0(0000) GS:ffff888125c46000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0ec3387ff8 CR3: 0000000061190000 CR4: 00000000003526f0
Call Trace:
<TASK>
invalidate_inode_pages2_range+0x62c/0xb30 mm/truncate.c:726
blkdev_direct_write+0x48/0x140 block/fops.c:690
blkdev_write_iter+0x530/0x700 block/fops.c:765
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x61e/0xbb0 fs/read_write.c:687
ksys_write+0x156/0x270 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0ec61fe0d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0ec4414028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f0ec6486180 RCX: 00007f0ec61fe0d9
RDX: 00000000ffffffdb RSI: 0000000000000000 RDI: 0000000000000008
RBP: 00007f0ec6295024 R08: 0000000000000000 R09: 0000000000000000
R13: 00007f0ec6486218 R14: 00007f0ec6486180 R15: 00007ffc8fc250d8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:folio_unmap_invalidate+0x7ee/0x830 mm/truncate.c:632
Code: c6 c0 71 78 8b e8 a2 e9 1d ff 90 0f 0b e8 3a f4 bb ff 48 89 df 48 c7 c6 c0 71 78 8b e8 8b e9 1d ff 90 0f 0b e8 23 f4 bb ff 90 <0f> 0b e8 1b f4 bb ff 48 89 df 48 c7 c6 c0 71 78 8b e8 6c e9 1d ff
RSP: 0018:ffffc900064a7830 EFLAGS: 00010287
RAX: ffffffff8209d53d RBX: ffffea0000b443c0 RCX: 0000000000080000
RDX: ffffc90013401000 RSI: 0000000000038e38 RDI: 0000000000038e39
RBP: ffffea0000b443c8 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff9400016887f R12: 0000000000000001
R13: dffffc0000000000 R14: 1ffffd4000168879 R15: 1ffffd4000168878
FS: 00007f0ec44146c0(0000) GS:ffff888125d46000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c240003 CR3: 0000000061190000 CR4: 00000000003526f0


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