syzbot


KCSAN: data-race in io_sq_thread / io_sq_thread_park (8)

Status: auto-obsoleted due to no activity on 2024/03/15 14:43
Subsystems: io-uring
[Documentation on labels]
Reported-by: syzbot+0b49ece9de95d7e19f25@syzkaller.appspotmail.com
First crash: 275d, last: 248d
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in io_sq_thread / io_sq_thread_park (5) io-uring 1 533d 533d 0/28 auto-obsoleted due to no activity on 2023/06/04 19:25
upstream KCSAN: data-race in io_sq_thread / io_sq_thread_park (9) io-uring 1 67d 63d 28/28 fixed on 2024/10/03 15:25
upstream KCSAN: data-race in io_sq_thread / io_sq_thread_park fs 13 862d 1030d 0/28 auto-closed as invalid on 2022/07/10 14:43
upstream KCSAN: data-race in io_sq_thread / io_sq_thread_park (4) io-uring 4 586d 627d 0/28 auto-obsoleted due to no activity on 2023/04/20 22:18
upstream KCSAN: data-race in io_sq_thread / io_sq_thread_park (2) io-uring 5 791d 827d 0/28 auto-closed as invalid on 2022/09/20 09:21
upstream KCSAN: data-race in io_sq_thread / io_sq_thread_park (6) io-uring 4 435d 481d 0/28 auto-obsoleted due to no activity on 2023/09/11 04:02
upstream KCSAN: data-race in io_sq_thread / io_sq_thread_park (7) io-uring 2 327d 309d 0/28 auto-obsoleted due to no activity on 2023/12/28 08:55
upstream KCSAN: data-race in io_sq_thread / io_sq_thread_park (3) io-uring 2 723d 751d 0/28 auto-obsoleted due to no activity on 2022/11/26 22:35

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

write to 0xffff888103dfa278 of 8 bytes by task 25078 on cpu 1:
 io_sq_thread+0xbd5/0xc50 io_uring/sqpoll.c:316
 ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

read to 0xffff888103dfa278 of 8 bytes by task 9825 on cpu 0:
 io_sq_thread_park+0x1b/0x80 io_uring/sqpoll.c:45
 io_ring_exit_work+0x178/0x500 io_uring/io_uring.c:3065
 process_one_work kernel/workqueue.c:2633 [inline]
 process_scheduled_works+0x5b8/0xa40 kernel/workqueue.c:2706
 worker_thread+0x525/0x730 kernel/workqueue.c:2787
 kthread+0x1d7/0x210 kernel/kthread.c:388
 ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

value changed: 0xffff88811b87c100 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 9825 Comm: kworker/u4:11 Not tainted 6.8.0-rc3-syzkaller-00136-g1f719a2f3fa6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
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
2024/02/09 14:42 upstream 1f719a2f3fa6 7f07e9b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in io_sq_thread / io_sq_thread_park
2024/01/14 09:32 upstream 052d534373b7 551587c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in io_sq_thread / io_sq_thread_park
* Struck through repros no longer work on HEAD.