syzbot

==================================================================
BUG: KCSAN: data-race in mas_replace_node / mtree_range_walk

write to 0xffff888104309c00 of 8 bytes by task 28239 on cpu 1:
 mte_set_node_dead lib/maple_tree.c:323 [inline]
 mas_put_in_tree lib/maple_tree.c:1726 [inline]
 mas_replace_node+0x1b5/0x440 lib/maple_tree.c:1740
 mas_wr_node_store lib/maple_tree.c:3956 [inline]
 mas_wr_modify+0x2bc3/0x3c90 lib/maple_tree.c:4189
 mas_wr_store_entry+0x250/0x390 lib/maple_tree.c:4229
 mas_store_prealloc+0x151/0x2b0 lib/maple_tree.c:5485
 vma_iter_store mm/internal.h:1292 [inline]
 vma_complete+0x3a7/0x760 mm/mmap.c:535
 __split_vma+0x58d/0x610 mm/mmap.c:2385
 split_vma mm/mmap.c:2411 [inline]
 vma_modify+0x10e/0x200 mm/mmap.c:2445
 vma_modify_flags include/linux/mm.h:3305 [inline]
 mprotect_fixup+0x322/0x5c0 mm/mprotect.c:635
 do_mprotect_pkey+0x655/0x940 mm/mprotect.c:809
 __do_sys_mprotect mm/mprotect.c:830 [inline]
 __se_sys_mprotect mm/mprotect.c:827 [inline]
 __x64_sys_mprotect+0x48/0x60 mm/mprotect.c:827
 x64_sys_call+0x26bd/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:11
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888104309c00 of 8 bytes by task 28240 on cpu 0:
 ma_dead_node lib/maple_tree.c:560 [inline]
 mtree_range_walk+0x33d/0x460 lib/maple_tree.c:2793
 mas_state_walk lib/maple_tree.c:3678 [inline]
 mas_walk+0x16e/0x320 lib/maple_tree.c:4909
 lock_vma_under_rcu+0x84/0x2a0 mm/memory.c:5758
 do_user_addr_fault arch/x86/mm/fault.c:1354 [inline]
 handle_page_fault arch/x86/mm/fault.c:1505 [inline]
 exc_page_fault+0x161/0x6d0 arch/x86/mm/fault.c:1563
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623

value changed: 0xffff888104309406 -> 0xffff888104309c00

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 28240 Comm: syz-executor.4 Not tainted 6.9.0-rc6-syzkaller-00290-gb9158815de52 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
==================================================================