[syzbot] [mm?] WARNING in __page_cache_release

[syzbot <syzbot+ba145f7f5f26bf2a11a2@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    897d54018cc9 Merge tag 'fbdev-for-7.1-rc1-2' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11c712ce580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d0f0911eedbc130a
dashboard link: https://syzkaller.appspot.com/bug?extid=ba145f7f5f26bf2a11a2
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: i386

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-897d5401.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/68d00820c9a1/vmlinux-897d5401.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c1ba47589ff2/bzImage-897d5401.xz

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

------------[ cut here ]------------
debug_locks && !(rcu_read_lock_held() || lock_is_held(&(&cgroup_mutex)->dep_map))
WARNING: ./include/linux/memcontrol.h:380 at obj_cgroup_memcg include/linux/memcontrol.h:380 [inline], CPU#1: dhcpcd-run-hook/5685
WARNING: ./include/linux/memcontrol.h:380 at folio_memcg include/linux/memcontrol.h:434 [inline], CPU#1: dhcpcd-run-hook/5685
WARNING: ./include/linux/memcontrol.h:380 at folio_matches_lruvec include/linux/memcontrol.h:1501 [inline], CPU#1: dhcpcd-run-hook/5685
WARNING: ./include/linux/memcontrol.h:380 at folio_lruvec_relock_irqsave include/linux/memcontrol.h:1523 [inline], CPU#1: dhcpcd-run-hook/5685
WARNING: ./include/linux/memcontrol.h:380 at __page_cache_release.part.0+0x1149/0x1440 mm/swap.c:77, CPU#1: dhcpcd-run-hook/5685
Modules linked in:
CPU: 1 UID: 0 PID: 5685 Comm: dhcpcd-run-hook Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:obj_cgroup_memcg include/linux/memcontrol.h:380 [inline]
RIP: 0010:folio_memcg include/linux/memcontrol.h:434 [inline]
RIP: 0010:folio_matches_lruvec include/linux/memcontrol.h:1501 [inline]
RIP: 0010:folio_lruvec_relock_irqsave include/linux/memcontrol.h:1523 [inline]
RIP: 0010:__page_cache_release.part.0+0x1149/0x1440 mm/swap.c:77
Code: 00 0f 85 b2 02 00 00 89 c6 31 ff 89 44 24 08 49 8b 2c 24 e8 29 a8 c0 ff 8b 44 24 08 85 c0 0f 85 34 fa ff ff e8 68 ad c0 ff 90 <0f> 0b 90 e9 26 fa ff ff e8 5a ad c0 ff 48 c7 c6 c0 a0 bd 8b 48 89
RSP: 0018:ffffc900045af6f8 EFLAGS: 00010093
RAX: 0000000000000000 RBX: ffffea00014fe100 RCX: ffffffff82472de7
RDX: ffff888027be4a00 RSI: ffffffff82472df8 RDI: ffff888027be4a00
RBP: ffff8880404a0048 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffc900045af7a8
R13: ffffc900045af7c8 R14: ffff88801b8ffe00 R15: 00000000000000ff
FS:  0000000000000000(0000) GS:ffff888097280000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1d72d36368 CR3: 0000000052fd2000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 __page_cache_release mm/swap.c:1009 [inline]
 folios_put_refs+0x780/0xa90 mm/swap.c:993
 free_pages_and_swap_cache+0x22d/0x3b0 mm/swap_state.c:401
 __tlb_batch_free_encoded_pages+0xe9/0x280 mm/mmu_gather.c:138
 tlb_batch_pages_flush mm/mmu_gather.c:151 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:417 [inline]
 tlb_flush_mmu mm/mmu_gather.c:424 [inline]
 tlb_finish_mmu+0x1b0/0x810 mm/mmu_gather.c:549
 exit_mmap+0x454/0xa10 mm/mmap.c:1313
 __mmput+0x12a/0x410 kernel/fork.c:1178
 mmput+0x67/0x80 kernel/fork.c:1201
 exit_mm kernel/exit.c:581 [inline]
 do_exit+0x833/0x2a60 kernel/exit.c:963
 do_group_exit+0xd5/0x2a0 kernel/exit.c:1117
 __do_sys_exit_group kernel/exit.c:1128 [inline]
 __se_sys_exit_group kernel/exit.c:1126 [inline]
 __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1126
 x64_sys_call+0x102c/0x1530 arch/x86/include/generated/asm/syscalls_64.h:232
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x10b/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1d72b666c5
Code: Unable to access opcode bytes at 0x7f1d72b6669b.
RSP: 002b:00007ffd91878108 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007ffd91878404 RCX: 00007f1d72b666c5
RDX: 00000000000000e7 RSI: ffffffffffffff88 RDI: 0000000000000000
RBP: 0000000000000003 R08: 00007ffd91878200 R09: 0000000000000002
R10: 00007f1d72c0cfe0 R11: 0000000000000202 R12: 0000000000000000
R13: 00007ffd91878440 R14: 00007f1d72d76000 R15: 000056441d2c7d98
 </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 syzkaller@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