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

10 views
Skip to first unread message

syzbot

unread,
Sep 19, 2023, 3:11:08 PM9/19/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 23f108dc9ed2 Merge tag 'tpmdd-v6.6-rc2' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=175ec854680000
kernel config: https://syzkaller.appspot.com/x/.config?x=60394d520e3d8e59
dashboard link: https://syzkaller.appspot.com/bug?extid=7ea26dbb28b9d69e4c4b
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/9ebf100d1910/disk-23f108dc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2b56a03b863f/vmlinux-23f108dc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/72e1e204e9dc/bzImage-23f108dc.xz

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

==================================================================
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
==================================================================


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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

syzbot

unread,
Oct 18, 2023, 7:09:48 PM10/18/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages