[moderation] [mm?] KCSAN: data-race in exec_mmap / vms_clear_ptes (2)

5 views
Skip to first unread message

syzbot

unread,
Nov 26, 2024, 4:33:26 AM11/26/24
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2c22dc1ee3a1 Merge tag 'mailbox-v6.13' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=102a5ff7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=db310a9aeec0c8cb
dashboard link: https://syzkaller.appspot.com/bug?extid=ad878f7158de844a3172
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [Liam.H...@oracle.com ak...@linux-foundation.org ja...@google.com linux-...@vger.kernel.org linu...@kvack.org lorenzo...@oracle.com vba...@suse.cz]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0cb07ee98241/disk-2c22dc1e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ba989cf0a9bd/vmlinux-2c22dc1e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b7e2933ec9ca/bzImage-2c22dc1e.xz

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

==================================================================
BUG: KCSAN: data-race in exec_mmap / vms_clear_ptes

write to 0xffff888101fd4638 of 8 bytes by task 3059 on cpu 0:
update_hiwater_rss include/linux/mm.h:2666 [inline]
vms_clear_ptes+0x1a7/0x300 mm/vma.c:1135
vms_complete_munmap_vmas+0x16c/0x470 mm/vma.c:1185
do_vmi_align_munmap+0x344/0x390 mm/vma.c:1444
do_vmi_munmap+0x1eb/0x230 mm/vma.c:1492
__vm_munmap+0xfd/0x220 mm/mmap.c:1367
__do_sys_munmap mm/mmap.c:1384 [inline]
__se_sys_munmap mm/mmap.c:1381 [inline]
__x64_sys_munmap+0x36/0x40 mm/mmap.c:1381
x64_sys_call+0xe14/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:12
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 0xffff888101fd4638 of 8 bytes by task 4086 on cpu 1:
get_mm_hiwater_rss include/linux/mm.h:2653 [inline]
setmax_mm_hiwater_rss include/linux/mm.h:2683 [inline]
exec_mmap+0x35c/0x4d0 fs/exec.c:1012
begin_new_exec+0xaf9/0x10b0 fs/exec.c:1270
load_elf_binary+0x63b/0x19e0 fs/binfmt_elf.c:1002
search_binary_handler fs/exec.c:1742 [inline]
exec_binprm fs/exec.c:1784 [inline]
bprm_execve+0x4e6/0xc30 fs/exec.c:1835
do_execveat_common+0x793/0x800 fs/exec.c:1942
do_execve fs/exec.c:2016 [inline]
__do_sys_execve fs/exec.c:2092 [inline]
__se_sys_execve fs/exec.c:2087 [inline]
__x64_sys_execve+0x5a/0x70 fs/exec.c:2087
x64_sys_call+0x1333/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:60
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: 0x0000000000000262 -> 0x0000000000000282

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 4086 Comm: dhcpcd Not tainted 6.12.0-syzkaller-09435-g2c22dc1ee3a1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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

syzbot

unread,
Feb 8, 2025, 7:05:16 PM2/8/25
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages