syzbot


KCSAN: data-race in io_ring_exit_work / io_sq_thread

Status: auto-closed as invalid on 2021/06/06 01:40
Subsystems: fs
[Documentation on labels]
First crash: 1104d, last: 1090d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in io_ring_exit_work / io_sq_thread (2) fs 20 910d 1048d 0/26 auto-closed as invalid on 2021/12/03 06:38

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

write to 0xffff88811cd864b8 of 8 bytes by task 19541 on cpu 0:
 io_sq_thread+0xf8d/0x10b0 fs/io_uring.c:6906
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

read to 0xffff88811cd864b8 of 8 bytes by task 4483 on cpu 1:
 io_sq_thread_park fs/io_uring.c:7234 [inline]
 io_ring_exit_work+0xa2/0x10e0 fs/io_uring.c:8716
 process_one_work+0x3e9/0x8f0 kernel/workqueue.c:2275
 worker_thread+0x636/0xae0 kernel/workqueue.c:2421
 kthread+0x1d0/0x1f0 kernel/kthread.c:313
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 4483 Comm: kworker/u4:9 Not tainted 5.12.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_unbound io_ring_exit_work
==================================================================

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/05/02 01:38 upstream 10a3efd0fee5 77e2b668 .config console log report info ci2-upstream-kcsan-gce KCSAN: data-race in io_ring_exit_work / io_sq_thread
2021/04/18 05:40 upstream 194cf4825638 7e2b734b .config console log report info ci2-upstream-kcsan-gce KCSAN: data-race in io_ring_exit_work / io_sq_thread
* Struck through repros no longer work on HEAD.