[moderation] [mm?] KCSAN: data-race in mas_state_walk / mas_wmb_replace (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 33cc938e65a9 Linux 6.7-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10ee7ce2e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ac34c1f29a8029df
dashboard link: https://syzkaller.appspot.com/bug?extid=c5c725faef78f5abb28a
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/6a0655688b57/disk-33cc938e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/89a66df4cc89/vmlinux-33cc938e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/621e82bbfa03/bzImage-33cc938e.xz

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

==================================================================
BUG: KCSAN: data-race in mas_state_walk / mas_wmb_replace

write to 0xffff888103efc000 of 8 bytes by task 3968 on cpu 0:
mte_set_node_dead lib/maple_tree.c:320 [inline]
mas_put_in_tree lib/maple_tree.c:1746 [inline]
mas_topiary_replace lib/maple_tree.c:2587 [inline]
mas_wmb_replace+0x214/0x14a0 lib/maple_tree.c:2678
mas_spanning_rebalance+0x275c/0x2d10 lib/maple_tree.c:2977
mas_wr_spanning_store+0x199f/0x1da0 lib/maple_tree.c:3909
mas_wr_store_entry+0x2b2/0x350 lib/maple_tree.c:4257
mas_store_prealloc+0x155/0x2b0 lib/maple_tree.c:5460
vma_iter_store+0xcb/0xe0 mm/internal.h:1198
vma_merge+0xc0f/0x12c0 mm/mmap.c:1028
vma_modify+0xb0/0x240 mm/mmap.c:2465
vma_modify_flags include/linux/mm.h:3271 [inline]
mprotect_fixup+0x324/0x5c0 mm/mprotect.c:635
do_mprotect_pkey+0x641/0x920 mm/mprotect.c:809
__do_sys_mprotect mm/mprotect.c:830 [inline]
__se_sys_mprotect mm/mprotect.c:827 [inline]
__x64_sys_mprotect+0x48/0x50 mm/mprotect.c:827
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 0xffff888103efc000 of 8 bytes by task 3969 on cpu 1:
ma_dead_node lib/maple_tree.c:555 [inline]
mtree_range_walk lib/maple_tree.c:2805 [inline]
mas_state_walk+0x267/0x5d0 lib/maple_tree.c:3712
mas_walk+0x31/0x120 lib/maple_tree.c:4888
lock_vma_under_rcu+0x8d/0x2a0 mm/memory.c:5496
do_user_addr_fault arch/x86/mm/fault.c:1356 [inline]
handle_page_fault arch/x86/mm/fault.c:1505 [inline]
exc_page_fault+0x164/0x6c0 arch/x86/mm/fault.c:1561
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570

value changed: 0xffff88813738b4c1 -> 0xffff888103efc000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 3969 Comm: syz-executor.4 Tainted: G W 6.7.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
==================================================================
loop4: detected capacity change from 0 to 2048


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