[moderation] [mm?] KCSAN: data-race in do_try_to_free_pages / shrink_node (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6bc40e44f1dd Merge tag 'ovl-fixes-6.7-rc2' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1014d267680000
kernel config: https://syzkaller.appspot.com/x/.config?x=a91f789b98394377
dashboard link: https://syzkaller.appspot.com/bug?extid=7564528c35043eec9e3c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4c54159bb579/disk-6bc40e44.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3a252c242f68/vmlinux-6bc40e44.xz
kernel image: https://storage.googleapis.com/syzbot-assets/235f427df017/bzImage-6bc40e44.xz

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

==================================================================
BUG: KCSAN: data-race in do_try_to_free_pages / shrink_node

write to 0xffff888107e13870 of 8 bytes by task 18154 on cpu 1:
snapshot_refaults mm/vmscan.c:6109 [inline]
do_try_to_free_pages+0x95f/0xce0 mm/vmscan.c:6171
try_to_free_mem_cgroup_pages+0x1e2/0x480 mm/vmscan.c:6463
try_charge_memcg+0x280/0xd30 mm/memcontrol.c:2742
obj_cgroup_charge_pages+0xab/0x130 mm/memcontrol.c:3254
__memcg_kmem_charge_page+0x9c/0x170 mm/memcontrol.c:3280
__alloc_pages+0x1bb/0x340 mm/page_alloc.c:4585
alloc_pages_mpol+0xb1/0x1d0 mm/mempolicy.c:2133
alloc_pages+0xe0/0x100 mm/mempolicy.c:2204
vm_area_alloc_pages mm/vmalloc.c:3063 [inline]
__vmalloc_area_node mm/vmalloc.c:3139 [inline]
__vmalloc_node_range+0x6d2/0xea0 mm/vmalloc.c:3320
kvmalloc_node+0x121/0x160 mm/util.c:632
kvmalloc include/linux/slab.h:738 [inline]
xt_alloc_table_info+0x3d/0x80 net/netfilter/x_tables.c:1192
do_replace net/ipv4/netfilter/arp_tables.c:970 [inline]
do_arpt_set_ctl+0x634/0x13b0 net/ipv4/netfilter/arp_tables.c:1421
nf_setsockopt+0x18d/0x1b0 net/netfilter/nf_sockopt.c:101
ip_setsockopt+0xe6/0x100 net/ipv4/ip_sockglue.c:1426
tcp_setsockopt+0x90/0xa0 net/ipv4/tcp.c:3704
sock_common_setsockopt+0x61/0x70 net/core/sock.c:3711
do_sock_setsockopt net/socket.c:2311 [inline]
__sys_setsockopt+0x1d4/0x240 net/socket.c:2334
__do_sys_setsockopt net/socket.c:2343 [inline]
__se_sys_setsockopt net/socket.c:2340 [inline]
__x64_sys_setsockopt+0x66/0x80 net/socket.c:2340
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff888107e13870 of 8 bytes by task 18153 on cpu 0:
prepare_scan_control mm/vmscan.c:2249 [inline]
shrink_node+0x3b3/0x15c0 mm/vmscan.c:5845
shrink_zones mm/vmscan.c:6086 [inline]
do_try_to_free_pages+0x43d/0xce0 mm/vmscan.c:6148
try_to_free_mem_cgroup_pages+0x1e2/0x480 mm/vmscan.c:6463
try_charge_memcg+0x280/0xd30 mm/memcontrol.c:2742
try_charge mm/memcontrol.c:2884 [inline]
charge_memcg mm/memcontrol.c:7209 [inline]
mem_cgroup_swapin_charge_folio+0x107/0x190 mm/memcontrol.c:7294
__read_swap_cache_async+0x2f6/0x550 mm/swap_state.c:490
swap_cluster_readahead+0x27c/0x4c0 mm/swap_state.c:655
swapin_readahead+0xe9/0x7f0 mm/swap_state.c:878
do_swap_page+0x4a0/0x1670 mm/memory.c:3883
handle_pte_fault mm/memory.c:5041 [inline]
__handle_mm_fault mm/memory.c:5179 [inline]
handle_mm_fault+0xa36/0x2dd0 mm/memory.c:5344
do_user_addr_fault arch/x86/mm/fault.c:1364 [inline]
handle_page_fault arch/x86/mm/fault.c:1505 [inline]
exc_page_fault+0x3ff/0x6c0 arch/x86/mm/fault.c:1561
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570

value changed: 0x0000000000000016 -> 0x0000000000000018

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 18153 Comm: syz-executor.0 Not tainted 6.7.0-rc1-syzkaller-00139-g6bc40e44f1dd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
==================================================================


---
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.