syzbot


KCSAN: data-race in loop_kthread_worker_fn / mm_update_next_owner

Status: auto-closed as invalid on 2021/02/16 14:57
Subsystems: block
[Documentation on labels]
First crash: 1200d, last: 1200d

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

read-write to 0xffff88810e5f002c of 4 bytes by task 26112 on cpu 0:
 loop_kthread_worker_fn+0x26/0x40 drivers/block/loop.c:931
 kthread+0x1fd/0x220 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

read to 0xffff88810e5f002c of 4 bytes by task 26113 on cpu 1:
 mm_update_next_owner+0x1d9/0x4e0 kernel/exit.c:388
 exit_mm+0x327/0x420 kernel/exit.c:500
 do_exit+0x41f/0x1690 kernel/exit.c:812
 do_group_exit+0x16f/0x170 kernel/exit.c:922
 __do_sys_exit_group+0xb/0x10 kernel/exit.c:933
 __se_sys_exit_group+0x5/0x10 kernel/exit.c:931
 __x64_sys_exit_group+0x16/0x20 kernel/exit.c:931
 do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x44/0xa9

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 26113 Comm: syz-executor.1 Not tainted 5.11.0-rc3-syzkaller #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
2021/01/12 14:54 upstream a0d54b4f5b21 2c1f2513 .config console log report info ci2-upstream-kcsan-gce
* Struck through repros no longer work on HEAD.