[moderation] [io-uring?] KCSAN: data-race in __se_sys_io_uring_register / io_sqe_buffers_register

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 052d534373b7 Merge tag 'exfat-for-6.8-rc1' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=146d41a3e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=adb08aaa4585df88
dashboard link: https://syzkaller.appspot.com/bug?extid=08e2774bc70dd101c90c
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/475d9c925209/disk-052d5343.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1aa974d3b699/vmlinux-052d5343.xz
kernel image: https://storage.googleapis.com/syzbot-assets/046680ef4c9b/bzImage-052d5343.xz

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

==================================================================
BUG: KCSAN: data-race in __se_sys_io_uring_register / io_sqe_buffers_register

read-write to 0xffff888160c7b0a4 of 4 bytes by task 32395 on cpu 1:
io_sqe_buffers_register+0x29d/0x390 io_uring/rsrc.c:1028
io_register_rsrc+0x1b5/0x1e0 io_uring/rsrc.c:548
__do_sys_io_uring_register io_uring/register.c:598 [inline]
__se_sys_io_uring_register+0x956/0x10e0 io_uring/register.c:559
__x64_sys_io_uring_register+0x55/0x60 io_uring/register.c:559
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x59/0x120 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff888160c7b0a4 of 4 bytes by task 32396 on cpu 0:
__do_sys_io_uring_register io_uring/register.c:600 [inline]
__se_sys_io_uring_register+0xa06/0x10e0 io_uring/register.c:559
__x64_sys_io_uring_register+0x55/0x60 io_uring/register.c:559
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x59/0x120 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00000000 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 32396 Comm: syz-executor.2 Tainted: G W 6.7.0-syzkaller-09928-g052d534373b7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/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 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.