[v6.1] WARNING in filemap_unaccount_folio (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 58485ff1a74f Linux 6.1.141
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14243e82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c186557a18643a0b
dashboard link: https://syzkaller.appspot.com/bug?extid=99e0ee0b072d0e6cf11c
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/467cd5b7e60b/disk-58485ff1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/df87a7313b47/vmlinux-58485ff1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/597ae3da22ce/bzImage-58485ff1.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 32090 at mm/filemap.c:208 filemap_unaccount_folio+0x507/0xa80 mm/filemap.c:207
Modules linked in:
CPU: 1 PID: 32090 Comm: syz.2.12270 Not tainted 6.1.141-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:filemap_unaccount_folio+0x507/0xa80 mm/filemap.c:207
Code: ee 83 e6 01 31 ff e8 e8 fc d5 ff 40 f6 c5 01 75 14 e8 7d f9 d5 ff 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 69 f9 d5 ff <0f> 0b 48 b8 00 00 00 00 00 fc ff df 41 80 3c 06 00 74 08 4c 89 e7
RSP: 0018:ffffc9000caaf798 EFLAGS: 00010083
RAX: ffffffff81aadd07 RBX: ffffea00010dba00 RCX: 0000000000080000
RDX: ffffc900052b1000 RSI: 000000000001aa79 RDI: 000000000001aa7a
RBP: 0000000000000003 R08: dffffc0000000000 R09: fffff9400021b741
R10: fffff9400021b741 R11: 1ffffd400021b740 R12: ffff8880179049f8
R13: 1ffffd400021b740 R14: 1ffff11002f2093f R15: ffffea00010dba08
FS: 00007feaa3d2b6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fca6f9b7bac CR3: 000000002f45b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
delete_from_page_cache_batch+0x14d/0xa50 mm/filemap.c:332
truncate_inode_pages_range+0x270/0xff0 mm/truncate.c:369
kill_bdev block/bdev.c:76 [inline]
set_blocksize+0x2da/0x350 block/bdev.c:152
swsusp_check+0xf6/0x450 kernel/power/swap.c:1529
software_resume+0x10e/0x6a0 kernel/power/hibernate.c:1000
resume_store+0xf7/0x1a0 kernel/power/hibernate.c:1205
kernfs_fop_write_iter+0x379/0x4c0 fs/kernfs/file.c:334
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x44c/0x960 fs/read_write.c:584
ksys_write+0x143/0x240 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7feaa2f8e929
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:00007feaa3d2b038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007feaa31b5fa0 RCX: 00007feaa2f8e929
RDX: 0000000000000012 RSI: 0000200000000000 RDI: 0000000000000003
RBP: 00007feaa3010b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007feaa31b5fa0 R15: 00007ffe5337ba98
</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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.