[moderation] [mm?] KCSAN: data-race in isolate_migratepages_block / isolate_migratepages_block (9)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2f8c4f506285 Merge tag 'auxdisplay-for-v6.11-tag1' of git:..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=145730d3980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7398409c79c30d03
dashboard link: https://syzkaller.appspot.com/bug?extid=cfbb1471fccd03b4dd8b
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/6165da49b7f1/disk-2f8c4f50.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/74fed2ebd154/vmlinux-2f8c4f50.xz
kernel image: https://storage.googleapis.com/syzbot-assets/32a1190d3a94/bzImage-2f8c4f50.xz

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

==================================================================
BUG: KCSAN: data-race in isolate_migratepages_block / isolate_migratepages_block

write to 0xffff88823fffab90 of 8 bytes by task 366 on cpu 1:
update_cached_migrate mm/compaction.c:504 [inline]
isolate_migratepages_block+0x24a5/0x2740 mm/compaction.c:1358
isolate_migratepages mm/compaction.c:2194 [inline]
compact_zone+0x1e1e/0x2930 mm/compaction.c:2641
compact_zone_order mm/compaction.c:2806 [inline]
try_to_compact_pages+0x388/0x920 mm/compaction.c:2862
__alloc_pages_direct_compact+0x6f/0x1e0 mm/page_alloc.c:3651
__alloc_pages_slowpath+0x236/0xd70 mm/page_alloc.c:4246
__alloc_pages_noprof+0x26d/0x360 mm/page_alloc.c:4709
alloc_pages_mpol_noprof+0xb1/0x1e0 mm/mempolicy.c:2263
alloc_pages_noprof+0xe1/0x100 mm/mempolicy.c:2343
vm_area_alloc_pages mm/vmalloc.c:3584 [inline]
__vmalloc_area_node mm/vmalloc.c:3660 [inline]
__vmalloc_node_range_noprof+0x719/0xef0 mm/vmalloc.c:3841
__kvmalloc_node_noprof+0x121/0x170 mm/util.c:675
kvmalloc_array_node_noprof include/linux/slab.h:833 [inline]
xt_alloc_entry_offsets+0x47/0x50 net/netfilter/x_tables.c:968
translate_table+0xa3/0xf70 net/ipv4/netfilter/ip_tables.c:678
do_replace net/ipv4/netfilter/ip_tables.c:1137 [inline]
do_ipt_set_ctl+0x7bd/0x8b0 net/ipv4/netfilter/ip_tables.c:1635
nf_setsockopt+0x195/0x1b0 net/netfilter/nf_sockopt.c:101
ip_setsockopt+0xea/0x100 net/ipv4/ip_sockglue.c:1424
tcp_setsockopt+0x93/0xb0 net/ipv4/tcp.c:3768
sock_common_setsockopt+0x64/0x80 net/core/sock.c:3735
smc_setsockopt+0x182/0x7a0 net/smc/af_smc.c:3072
do_sock_setsockopt net/socket.c:2324 [inline]
__sys_setsockopt+0x1d8/0x250 net/socket.c:2347
__do_sys_setsockopt net/socket.c:2356 [inline]
__se_sys_setsockopt net/socket.c:2353 [inline]
__x64_sys_setsockopt+0x66/0x80 net/socket.c:2353
x64_sys_call+0x2a0e/0x2e00 arch/x86/include/generated/asm/syscalls_64.h:55
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88823fffab90 of 8 bytes by task 32 on cpu 0:
update_cached_migrate mm/compaction.c:503 [inline]
isolate_migratepages_block+0x2481/0x2740 mm/compaction.c:1358
isolate_migratepages mm/compaction.c:2194 [inline]
compact_zone+0x1e1e/0x2930 mm/compaction.c:2641
kcompactd_do_work mm/compaction.c:3112 [inline]
kcompactd+0x4e0/0xd40 mm/compaction.c:3211
kthread+0x1d1/0x210 kernel/kthread.c:389
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

value changed: 0x0000000000228600 -> 0x0000000000229a00

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 32 Comm: kcompactd0 Not tainted 6.10.0-syzkaller-12708-g2f8c4f506285 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
==================================================================


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