syzbot


KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (7)

Status: auto-obsoleted due to no activity on 2023/10/18 23:09
Subsystems: io-uring
[Documentation on labels]
Reported-by: syzbot+7ea26dbb28b9d69e4c4b@syzkaller.appspotmail.com
First crash: 231d, last: 231d
Similar bugs (9)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (3) fs 2 914d 922d 0/26 auto-closed as invalid on 2021/12/05 08:50
upstream KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (5) fs 2 754d 758d 0/26 auto-closed as invalid on 2022/05/14 09:20
upstream KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (10) io-uring 1 5h46m 5h45m 0/26 moderation: reported on 2024/05/02 09:26
upstream KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (2) fs 1 1021d 1021d 0/26 auto-closed as invalid on 2021/08/20 00:41
upstream KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (4) fs 3 804d 833d 0/26 auto-closed as invalid on 2022/03/25 11:59
upstream KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests fs 1 1088d 1088d 0/26 auto-closed as invalid on 2021/06/13 15:29
upstream KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (9) io-uring 2 73d 91d 0/26 auto-obsoleted due to no activity on 2024/03/25 07:41
upstream KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (8) io-uring 1 162d 142d 0/26 auto-obsoleted due to no activity on 2023/12/27 04:40
upstream KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (6) io-uring 2 628d 651d 0/26 auto-closed as invalid on 2022/09/17 04:56

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

write to 0xffff888136700038 of 8 bytes by task 21938 on cpu 0:
 io_sq_thread+0xb03/0xb80 io_uring/sqpoll.c:308
 ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304

read to 0xffff888136700038 of 8 bytes by task 5927 on cpu 1:
 io_uring_try_cancel_requests+0x1b7/0x440 io_uring/io_uring.c:3292
 io_ring_exit_work+0x126/0x4f0 io_uring/io_uring.c:3079
 process_one_work kernel/workqueue.c:2630 [inline]
 process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703
 worker_thread+0x525/0x730 kernel/workqueue.c:2784
 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:304

value changed: 0xffff8881070230c0 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 5927 Comm: kworker/u4:7 Tainted: G        W          6.6.0-rc1-syzkaller-00070-g23f108dc9ed2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
Workqueue: events_unbound io_ring_exit_work
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/09/13 23:09 upstream 23f108dc9ed2 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests
* Struck through repros no longer work on HEAD.