syzbot


KCSAN: data-race in __do_sys_prctl / __do_sys_prctl

Status: auto-closed as invalid on 2022/04/29 05:00
Subsystems: kernel
[Documentation on labels]
First crash: 763d, last: 763d

Sample crash report:
==================================================================
BUG: KCSAN: data-race in __do_sys_prctl / __do_sys_prctl

write to 0xffff888103e8d280 of 1 bytes by task 4527 on cpu 0:
 __do_sys_prctl+0x38e/0xcb0 kernel/sys.c:2492
 __se_sys_prctl kernel/sys.c:2342 [inline]
 __x64_sys_prctl+0x62/0x70 kernel/sys.c:2342
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888103e8d280 of 1 bytes by task 4528 on cpu 1:
 __do_sys_prctl+0x377/0xcb0 kernel/sys.c:2492
 __se_sys_prctl kernel/sys.c:2342 [inline]
 __x64_sys_prctl+0x62/0x70 kernel/sys.c:2342
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x01 -> 0x00

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 4528 Comm: syz-executor.5 Not tainted 5.17.0-syzkaller-07593-g52deda9551a0-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/03/25 04:58 upstream 52deda9551a0 89bc8608 .config console log report info ci2-upstream-kcsan-gce KCSAN: data-race in __do_sys_prctl / __do_sys_prctl
* Struck through repros no longer work on HEAD.