syzbot


KCSAN: data-race in getrusage / handle_mm_fault

Status: auto-closed as invalid on 2022/04/04 19:24
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 273d, last: 273d

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

write to 0xffff8881186d0e80 of 8 bytes by task 22488 on cpu 1:
 mm_account_fault mm/memory.c:4753 [inline]
 handle_mm_fault+0x10e1/0x1590 mm/memory.c:4817
 do_user_addr_fault+0x617/0xb90 arch/x86/mm/fault.c:1397
 handle_page_fault arch/x86/mm/fault.c:1484 [inline]
 exc_page_fault+0x91/0x290 arch/x86/mm/fault.c:1540
 asm_exc_page_fault+0x1e/0x30

read to 0xffff8881186d0e80 of 8 bytes by task 22493 on cpu 0:
 accumulate_thread_rusage kernel/sys.c:1742 [inline]
 getrusage+0x78c/0xa70 kernel/sys.c:1799
 __do_sys_getrusage kernel/sys.c:1831 [inline]
 __se_sys_getrusage kernel/sys.c:1823 [inline]
 __x64_sys_getrusage+0x9c/0x100 kernel/sys.c:1823
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x000000000000001d -> 0x000000000000001e

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

Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-kcsan-gce 2022/02/28 18:56 upstream 7e57714cd0ad 45a13a73 .config log report info KCSAN: data-race in getrusage / handle_mm_fault
* Struck through repros no longer work on HEAD.