[v6.6] WARNING in folio_lruvec_lock_irqsave

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a5df3a702b2c Linux 6.6.96
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1627d582580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2632deddafa957e8
dashboard link: https://syzkaller.appspot.com/bug?extid=72c4de24506ec4faf004
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9ba5b19f9f4d/disk-a5df3a70.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2cd779015729/vmlinux-a5df3a70.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b56fc39e5cb8/bzImage-a5df3a70.xz

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

erofs_put_super+0x7b/0x150 fs/erofs/super.c:815
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
erofs_kill_sb+0x4c/0x140 fs/erofs/super.c:794
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6589 at include/linux/memcontrol.h:764 folio_lruvec include/linux/memcontrol.h:764 [inline]
WARNING: CPU: 0 PID: 6589 at include/linux/memcontrol.h:764 folio_lruvec_lock_irqsave+0x212/0x270 mm/memcontrol.c:1369
Modules linked in:
CPU: 0 PID: 6589 Comm: syz.4.138 Not tainted 6.6.96-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:folio_lruvec include/linux/memcontrol.h:764 [inline]
RIP: 0010:folio_lruvec_lock_irqsave+0x212/0x270 mm/memcontrol.c:1369
Code: 4c 89 f7 e8 10 20 f9 ff 48 8b 04 24 49 89 06 e9 1c ff ff ff 48 89 df 48 c7 c6 00 c7 b6 8a e8 75 9a e1 ff c6 05 af ff 4f 0c 01 <0f> 0b e9 1b fe ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 9d fe
RSP: 0018:ffffc900048ff1d8 EFLAGS: 00010246
RAX: 6f229c8ad52aa000 RBX: ffffea00017d7240 RCX: 6f229c8ad52aa000
RDX: 0000000000000002 RSI: ffffffff8aaac440 RDI: ffffffff8afc6d00
RBP: ffffc900048ff280 R08: ffffffff8e4a7faf R09: 1ffffffff1c94ff5
R10: dffffc0000000000 R11: fffffbfff1c94ff6 R12: ffff8880b8e36e48
R13: dffffc0000000000 R14: ffff888077472000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f711ff8 CR3: 000000005abad000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
folio_lruvec_relock_irqsave include/linux/memcontrol.h:1654 [inline]
folio_batch_move_lru+0x2d8/0x6b0 mm/swap.c:208
lru_add_drain_cpu+0x10e/0x8c0 mm/swap.c:644
lru_add_drain+0x121/0x3e0 mm/swap.c:744
free_pages_and_swap_cache+0x1c/0xa0 mm/swap_state.c:312
tlb_batch_pages_flush mm/mmu_gather.c:98 [inline]
tlb_flush_mmu_free mm/mmu_gather.c:293 [inline]
tlb_flush_mmu+0x368/0x4f0 mm/mmu_gather.c:300
zap_pte_range mm/memory.c:1531 [inline]
zap_pmd_range mm/memory.c:1570 [inline]
zap_pud_range mm/memory.c:1599 [inline]
zap_p4d_range mm/memory.c:1620 [inline]
unmap_page_range+0x26d4/0x2fe0 mm/memory.c:1641
unmap_vmas+0x25e/0x3a0 mm/memory.c:1731
exit_mmap+0x200/0xb50 mm/mmap.c:3298
__mmput+0x118/0x3c0 kernel/fork.c:1355
exit_mm+0x1da/0x2c0 kernel/exit.c:569
do_exit+0x88e/0x23c0 kernel/exit.c:870
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f8d0b58e929
Code: Unable to access opcode bytes at 0x7f8d0b58e8ff.
RSP: 002b:00007f8d0c3e70e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007f8d0b7b6088 RCX: 00007f8d0b58e929
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f8d0b7b6088
RBP: 00007f8d0b7b6080 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f8d0b7b608c
R13: 0000000000000000 R14: 00007fffaab67970 R15: 00007fffaab67a58
</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