[moderation] [io-uring?] KCSAN: data-race in __io_uring_show_fdinfo / io_submit_sqes

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 93f5de5f648d Merge tag 'acpi-6.5-rc8' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16aa420ba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f12c32a009b80107
dashboard link: https://syzkaller.appspot.com/bug?extid=ea81befdb933895e29c7
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/1f2b512883ff/disk-93f5de5f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e10aeb67696c/vmlinux-93f5de5f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3e95be907cb0/bzImage-93f5de5f.xz

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

==================================================================
BUG: KCSAN: data-race in __io_uring_show_fdinfo / io_submit_sqes

read-write to 0xffff888138a79870 of 4 bytes by task 15030 on cpu 1:
io_get_sqe io_uring/io_uring.c:2365 [inline]
io_submit_sqes+0x23d/0xfb0 io_uring/io_uring.c:2411
__do_sys_io_uring_enter io_uring/io_uring.c:3628 [inline]
__se_sys_io_uring_enter+0x1f8/0x1c10 io_uring/io_uring.c:3562
__x64_sys_io_uring_enter+0x78/0x90 io_uring/io_uring.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

read to 0xffff888138a79870 of 4 bytes by task 15029 on cpu 0:
__io_uring_show_fdinfo+0x12d/0xd50 io_uring/fdinfo.c:80
io_uring_show_fdinfo+0x73/0x1c0 io_uring/fdinfo.c:212
seq_show+0x316/0x360 fs/proc/fd.c:70
seq_read_iter+0x2bc/0x8f0 fs/seq_file.c:230
seq_read+0xd8/0x120 fs/seq_file.c:162
vfs_read+0x19f/0x5c0 fs/read_write.c:468
ksys_read+0xeb/0x1a0 fs/read_write.c:613
__do_sys_read fs/read_write.c:623 [inline]
__se_sys_read fs/read_write.c:621 [inline]
__x64_sys_read+0x42/0x50 fs/read_write.c:621
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

value changed: 0x00002ba0 -> 0x00002bad

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 15029 Comm: syz-executor.3 Not tainted 6.5.0-rc7-syzkaller-00024-g93f5de5f648d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
==================================================================


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

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