[moderation] [io-uring?] KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests (10)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0106679839f7 Merge tag 'regulator-fix-v6.9-rc6' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10941e9b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c3beef2aff822313
dashboard link: https://syzkaller.appspot.com/bug?extid=938722c54478146b0ea0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [asml.s...@gmail.com ax...@kernel.dk io-u...@vger.kernel.org linux-...@vger.kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e3e2408ba3af/disk-01066798.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a35e4f19b317/vmlinux-01066798.xz
kernel image: https://storage.googleapis.com/syzbot-assets/534b6c55e4fa/bzImage-01066798.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+938722...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in io_sq_thread / io_uring_try_cancel_requests

write to 0xffff8881159fe0f8 of 8 bytes by task 15261 on cpu 1:
io_sq_thread+0xccf/0xef0 io_uring/sqpoll.c:373
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

read to 0xffff8881159fe0f8 of 8 bytes by task 11466 on cpu 0:
io_uring_try_cancel_requests+0x1e8/0x570 io_uring/io_uring.c:3308
io_ring_exit_work+0x126/0x500 io_uring/io_uring.c:3069
process_one_work kernel/workqueue.c:3267 [inline]
process_scheduled_works+0x465/0x990 kernel/workqueue.c:3348
worker_thread+0x526/0x730 kernel/workqueue.c:3429
kthread+0x1d1/0x210 kernel/kthread.c:388
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

value changed: 0xffff888138e66300 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 11466 Comm: kworker/u8:67 Tainted: G W 6.9.0-rc6-syzkaller-00053-g0106679839f7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: iou_exit io_ring_exit_work
==================================================================
vhci_hcd: stop threads
vhci_hcd: release socket
vhci_hcd: disconnect device
vhci_hcd: stop threads
vhci_hcd: release socket
vhci_hcd: disconnect device
vhci_hcd: stop threads
vhci_hcd: release socket
vhci_hcd: disconnect device
vhci_hcd: stop threads
vhci_hcd: release socket
vhci_hcd: disconnect device


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.