Hello, syzbot found the following issue on: HEAD commit: b311c1b497e5 Merge tag '6.11-rc4-server-fixes' of git://gi.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=140ca7c5980000 kernel config: https://syzkaller.appspot.com/x/.config?x=3aa0f597417bf8c7 dashboard link: https://syzkaller.appspot.com/bug?extid=6e54fc669e2c440731fd compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/806c87e93e26/disk-b311c1b4.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/73951ff34e6d/vmlinux-b311c1b4.xz kernel image: https://storage.googleapis.com/syzbot-assets/f4b7546a486d/bzImage-b311c1b4.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+6e54fc669e2c440731fd@xxxxxxxxxxxxxxxxxxxxxxxxx EXT4-fs (loop2): stripe (7) is not aligned with cluster size (16), stripe is disabled EXT4-fs (loop2): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. ================================================================== BUG: KCSAN: data-race in __reset_isolation_suitable / compact_zone write to 0xffff88823fffab90 of 8 bytes by task 77 on cpu 0: __reset_isolation_suitable+0x149/0x2b0 mm/compaction.c:438 reset_isolation_suitable+0xb2/0x100 mm/compaction.c:469 kswapd_try_to_sleep mm/vmscan.c:7084 [inline] kswapd+0x296/0x1820 mm/vmscan.c:7193 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 write to 0xffff88823fffab90 of 8 bytes by task 28833 on cpu 1: update_cached_migrate mm/compaction.c:504 [inline] isolate_migratepages mm/compaction.c:2189 [inline] compact_zone+0x1293/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:3650 __alloc_pages_slowpath+0x236/0xd70 mm/page_alloc.c:4245 __alloc_pages_noprof+0x26d/0x360 mm/page_alloc.c:4708 alloc_pages_preferred_many mm/mempolicy.c:2204 [inline] alloc_pages_mpol_noprof+0xec/0x1e0 mm/mempolicy.c:2228 alloc_pages_noprof+0xe1/0x100 mm/mempolicy.c:2343 vm_area_alloc_pages mm/vmalloc.c:3584 [inline] __vmalloc_area_node mm/vmalloc.c:3653 [inline] __vmalloc_node_range_noprof+0x736/0xec0 mm/vmalloc.c:3834 __kvmalloc_node_noprof+0x121/0x170 mm/util.c:675 ip_set_alloc+0x1f/0x30 net/netfilter/ipset/ip_set_core.c:256 hash_netiface_create+0x273/0x730 net/netfilter/ipset/ip_set_hash_gen.h:1568 ip_set_create+0x359/0x8a0 net/netfilter/ipset/ip_set_core.c:1104 nfnetlink_rcv_msg+0x4a9/0x570 net/netfilter/nfnetlink.c:302 netlink_rcv_skb+0x12c/0x230 net/netlink/af_netlink.c:2550 nfnetlink_rcv+0x16c/0x15e0 net/netfilter/nfnetlink.c:667 netlink_unicast_kernel net/netlink/af_netlink.c:1331 [inline] netlink_unicast+0x599/0x670 net/netlink/af_netlink.c:1357 netlink_sendmsg+0x5cc/0x6e0 net/netlink/af_netlink.c:1901 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0x140/0x180 net/socket.c:745 ____sys_sendmsg+0x312/0x410 net/socket.c:2597 ___sys_sendmsg net/socket.c:2651 [inline] __sys_sendmsg+0x1e9/0x280 net/socket.c:2680 __do_sys_sendmsg net/socket.c:2689 [inline] __se_sys_sendmsg net/socket.c:2687 [inline] __x64_sys_sendmsg+0x46/0x50 net/socket.c:2687 x64_sys_call+0x2689/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:47 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 value changed: 0x0000000000196e00 -> 0x0000000000105a00 Reported by Kernel Concurrency Sanitizer on: CPU: 1 UID: 0 PID: 28833 Comm: syz.2.8522 Not tainted 6.11.0-rc4-syzkaller-00019-gb311c1b497e5 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 ================================================================== EXT4-fs (loop2): unmounting filesystem 00000000-0000-0000-0000-000000000000. --- 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@xxxxxxxxxxxxxxxx. 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
