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

2 views
Skip to first unread message

syzbot

unread,
3:19 AM (13 hours ago) 3:19 AM
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: aec2f682d47c Merge tag 'v7.1-p1' of git://git.kernel.org/p..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13a70702580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9c2dc5e8c701bc54
dashboard link: https://syzkaller.appspot.com/bug?extid=7265211618d78be5c8e2
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
CC: [Liam.H...@oracle.com ak...@linux-foundation.org ja...@google.com linux-...@vger.kernel.org linu...@kvack.org l...@kernel.org pfal...@suse.de vba...@kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df8234344013/disk-aec2f682.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/76a15c74e7d7/vmlinux-aec2f682.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fa5d1bc9eef0/bzImage-aec2f682.xz

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

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

write to 0xffff888104895400 of 8 bytes by task 10165 on cpu 1:
mas_set_parent lib/maple_tree.c:495 [inline]
mas_adopt_children lib/maple_tree.c:1549 [inline]
mas_topiary_replace lib/maple_tree.c:1842 [inline]
mas_wmb_replace+0x908/0x1760 lib/maple_tree.c:2083
mas_wr_store_entry+0x54ff/0x5ad0 lib/maple_tree.c:-1
mas_store_prealloc+0x43e/0x690 lib/maple_tree.c:4936
vma_iter_store_overwrite mm/vma.h:616 [inline]
vma_iter_store_new mm/vma.h:623 [inline]
vma_complete+0x3c7/0x850 mm/vma.c:359
__split_vma+0x593/0x640 mm/vma.c:569
split_vma mm/vma.c:599 [inline]
vma_modify+0xb4b/0xca0 mm/vma.c:1691
vma_modify_flags+0x182/0x210 mm/vma.c:1719
mprotect_fixup+0x3a2/0x680 mm/mprotect.c:759
do_mprotect_pkey+0x6ae/0x960 mm/mprotect.c:937
__do_sys_mprotect mm/mprotect.c:958 [inline]
__se_sys_mprotect mm/mprotect.c:955 [inline]
__x64_sys_mprotect+0x48/0x60 mm/mprotect.c:955
x64_sys_call+0x2768/0x3020 arch/x86/include/generated/asm/syscalls_64.h:11
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x12c/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888104895400 of 8 bytes by task 10167 on cpu 0:
ma_dead_node lib/maple_tree.c:544 [inline]
mtree_range_walk+0x350/0x490 lib/maple_tree.c:2051
mas_state_walk lib/maple_tree.c:2952 [inline]
mas_walk+0x1cc/0x370 lib/maple_tree.c:4366
lock_vma_under_rcu+0xc9/0x210 mm/mmap_lock.c:304
do_user_addr_fault+0x232/0x1050 arch/x86/mm/fault.c:1325
handle_page_fault arch/x86/mm/fault.c:1474 [inline]
exc_page_fault+0x62/0xa0 arch/x86/mm/fault.c:1527
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618

value changed: 0xffff8881043ae216 -> 0xffff888101625016

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 10167 Comm: syz.4.2266 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
==================================================================


---
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
Reply all
Reply to author
Forward
0 new messages