Hello, syzbot found the following issue on: HEAD commit: 66cc544fd75c Merge tag 'dmaengine-fix-6.10' of git://git.k.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=128ed3da980000 kernel config: https://syzkaller.appspot.com/x/.config?x=704451bc2941bcb0 dashboard link: https://syzkaller.appspot.com/bug?extid=6a4002279343ac44c448 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/4b6f7aacd04c/disk-66cc544f.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/083bb1b69afe/vmlinux-66cc544f.xz kernel image: https://storage.googleapis.com/syzbot-assets/05a661578a53/bzImage-66cc544f.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+6a4002279343ac44c448@xxxxxxxxxxxxxxxxxxxxxxxxx ================================================================== BUG: KCSAN: data-race in io_submit_sqes / io_uring_poll read-write to 0xffff888107b41870 of 4 bytes by task 4848 on cpu 1: io_get_sqe io_uring/io_uring.c:2276 [inline] io_submit_sqes+0x23f/0x1080 io_uring/io_uring.c:2327 __do_sys_io_uring_enter io_uring/io_uring.c:3245 [inline] __se_sys_io_uring_enter+0x1c6/0x15a0 io_uring/io_uring.c:3182 __x64_sys_io_uring_enter+0x78/0x90 io_uring/io_uring.c:3182 x64_sys_call+0x25ab/0x2d70 arch/x86/include/generated/asm/syscalls_64.h:427 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f read to 0xffff888107b41870 of 4 bytes by task 4847 on cpu 0: io_sqring_full io_uring/io_uring.h:285 [inline] io_uring_poll+0xcf/0x190 io_uring/io_uring.c:2739 vfs_poll include/linux/poll.h:84 [inline] __io_arm_poll_handler+0x229/0xf30 io_uring/poll.c:622 io_arm_poll_handler+0x411/0x5d0 io_uring/poll.c:756 io_queue_async+0x89/0x320 io_uring/io_uring.c:1943 io_queue_sqe io_uring/io_uring.c:1972 [inline] io_req_task_submit+0xb3/0xc0 io_uring/io_uring.c:1385 io_handle_tw_list+0x1b9/0x200 io_uring/io_uring.c:1083 tctx_task_work_run+0x6c/0x1b0 io_uring/io_uring.c:1155 tctx_task_work+0x40/0x80 io_uring/io_uring.c:1173 task_work_run+0x13a/0x1a0 kernel/task_work.c:180 get_signal+0xeee/0x1080 kernel/signal.c:2681 arch_do_signal_or_restart+0x95/0x4b0 arch/x86/kernel/signal.c:310 exit_to_user_mode_loop kernel/entry/common.c:111 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x59/0x130 kernel/entry/common.c:218 do_syscall_64+0xd6/0x1c0 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f value changed: 0x000003b7 -> 0x000003d5 --- 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 syzkaller@xxxxxxxxxxxxxxxx. 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
