[moderation] [fs?] KCSAN: data-race in aio_read_events / iocb_put (12)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 379f604cc3dc Merge tag 'pci-v6.16-fixes-3' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1736fe8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2f5ccd29a82f8aa
dashboard link: https://syzkaller.appspot.com/bug?extid=71695ff2a8972d49d49b
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
CC: [bc...@kvack.org bra...@kernel.org ja...@suse.cz linu...@kvack.org linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/27263ef4b12c/disk-379f604c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/09ae95440294/vmlinux-379f604c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6ccdfad67a30/bzImage-379f604c.xz

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

==================================================================
BUG: KCSAN: data-race in aio_read_events / iocb_put

write to 0xffff8881627b500c of 4 bytes by task 8069 on cpu 0:
aio_complete fs/aio.c:1162 [inline]
iocb_put+0x199/0x6d0 fs/aio.c:1209
io_submit_one+0xad7/0x11d0 fs/aio.c:2056
__do_sys_io_submit fs/aio.c:2112 [inline]
__se_sys_io_submit+0xfb/0x280 fs/aio.c:2082
__x64_sys_io_submit+0x43/0x50 fs/aio.c:2082
x64_sys_call+0xfc4/0x2fb0 arch/x86/include/generated/asm/syscalls_64.h:210
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd2/0x200 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff8881627b500c of 4 bytes by task 8068 on cpu 1:
aio_read_events_ring fs/aio.c:1238 [inline]
aio_read_events+0xb2/0x400 fs/aio.c:1298
read_events fs/aio.c:1334 [inline]
do_io_getevents+0x11b/0x400 fs/aio.c:2230
__do_sys_io_getevents fs/aio.c:2263 [inline]
__se_sys_io_getevents fs/aio.c:2251 [inline]
__x64_sys_io_getevents+0xca/0x190 fs/aio.c:2251
x64_sys_call+0x29fc/0x2fb0 arch/x86/include/generated/asm/syscalls_64.h:209
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd2/0x200 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000017 -> 0x0000001a

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 8068 Comm: syz.7.1315 Not tainted 6.16.0-rc5-syzkaller-00224-g379f604cc3dc #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
==================================================================


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