[v6.1] WARNING in filemap_unaccount_folio

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 347385861c50 Linux 6.1.84
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12c32389180000
kernel config: https://syzkaller.appspot.com/x/.config?x=40dfd13b04bfc094
dashboard link: https://syzkaller.appspot.com/bug?extid=d4981bd6ef84e32f2d7b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/73d2a8622b6e/disk-34738586.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e7bc2e0101a7/vmlinux-34738586.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7b96d1168608/bzImage-34738586.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 4066 at mm/filemap.c:208 filemap_unaccount_folio+0x504/0xa60
Modules linked in:
CPU: 1 PID: 4066 Comm: syz-executor.2 Not tainted 6.1.84-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:filemap_unaccount_folio+0x504/0xa60 mm/filemap.c:207
Code: ee 83 e6 01 31 ff e8 2b b1 d3 ff 40 f6 c5 01 75 14 e8 c0 ad d3 ff 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 ac ad d3 ff <0f> 0b 48 b8 00 00 00 00 00 fc ff df 41 80 3c 06 00 74 08 48 89 df
RSP: 0018:ffffc900036e7758 EFLAGS: 00010087
RAX: ffffffff81b6d944 RBX: ffff8880128d3ef8 RCX: 0000000000040000
RDX: ffffc9000b28b000 RSI: 00000000000103fb RDI: 00000000000103fc
RBP: 0000000000000003 R08: ffffffff81b6d925 R09: fffff94000136eb1
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffffd4000136eb0
R13: ffffea00009b7580 R14: 1ffff1100251a7df R15: ffffea00009b7588
FS: 00007f7d8c3576c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000051a07000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
delete_from_page_cache_batch+0x16f/0xc90 mm/filemap.c:332
truncate_inode_pages_range+0x370/0x1340 mm/truncate.c:369
kill_bdev block/bdev.c:76 [inline]
set_blocksize+0x2d9/0x350 block/bdev.c:152
swsusp_check+0x11a/0x490 kernel/power/swap.c:1529
software_resume+0x124/0x680 kernel/power/hibernate.c:995
resume_store+0x105/0x1b0 kernel/power/hibernate.c:1200
kernfs_fop_write_iter+0x3a2/0x4f0 fs/kernfs/file.c:330
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x7ae/0xba0 fs/read_write.c:584
ksys_write+0x19c/0x2c0 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7d8b67de69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7d8c3570c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f7d8b7abf80 RCX: 00007f7d8b67de69
RDX: 0000000000000012 RSI: 00000000200001c0 RDI: 0000000000000005
RBP: 00007f7d8b6ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f7d8b7abf80 R15: 00007ffeba4f0e78
</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 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