================================================================== BUG: KCSAN: data-race in cgroup_rstat_flush_locked / cgroup_rstat_updated write to 0xffffe8ffffd193c0 of 8 bytes by task 36 on cpu 0: cgroup_rstat_cpu_pop_updated kernel/cgroup/rstat.c:139 [inline] cgroup_rstat_flush_locked+0x282/0x7f0 kernel/cgroup/rstat.c:161 cgroup_rstat_flush_irqsafe+0x24/0x40 kernel/cgroup/rstat.c:218 mem_cgroup_flush_stats mm/memcontrol.c:5354 [inline] flush_memcg_stats_work+0x34/0x60 mm/memcontrol.c:5366 process_one_work+0x402/0x910 kernel/workqueue.c:2297 worker_thread+0x636/0xae0 kernel/workqueue.c:2444 kthread+0x262/0x280 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 read to 0xffffe8ffffd193c0 of 8 bytes by task 1770 on cpu 1: cgroup_rstat_updated+0x53/0x1c0 kernel/cgroup/rstat.c:38 __count_memcg_events+0x43/0x50 mm/memcontrol.c:788 __activate_page+0x50c/0x5f0 mm/swap.c:309 pagevec_lru_move_fn+0x1c4/0x2d0 mm/swap.c:197 activate_page mm/swap.c:338 [inline] mark_page_accessed+0x485/0x550 mm/swap.c:422 zap_pte_range+0x5f3/0xe00 mm/memory.c:1359 zap_pmd_range mm/memory.c:1481 [inline] zap_pud_range mm/memory.c:1510 [inline] zap_p4d_range mm/memory.c:1531 [inline] unmap_page_range+0x2dc/0x3d0 mm/memory.c:1552 unmap_single_vma+0x157/0x210 mm/memory.c:1597 unmap_vmas+0xc0/0x170 mm/memory.c:1629 exit_mmap+0x22d/0x460 mm/mmap.c:3194 __mmput+0x27/0x1c0 kernel/fork.c:1103 mmput+0x3d/0x50 kernel/fork.c:1124 exit_mm+0x2f7/0x3f0 kernel/exit.c:501 do_exit+0x3ef/0x14a0 kernel/exit.c:812 do_group_exit+0xa4/0x1a0 kernel/exit.c:922 __do_sys_exit_group+0xb/0x10 kernel/exit.c:933 __se_sys_exit_group+0x5/0x10 kernel/exit.c:931 __x64_sys_exit_group+0x16/0x20 kernel/exit.c:931 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff888100c40010 -> 0x0000000000000000 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1770 Comm: syz-executor Not tainted 5.14.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 ==================================================================