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

0 views
Skip to first unread message

syzbot

unread,
May 12, 2024, 6:57:26 PM (11 days ago) May 12
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ba16c1cf11c9 Merge tag 'edac_urgent_for_v6.9' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11bda65c980000
kernel config: https://syzkaller.appspot.com/x/.config?x=168fab99759dff68
dashboard link: https://syzkaller.appspot.com/bug?extid=1c73a736a6465310b5cb
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
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/12cd098adb5d/disk-ba16c1cf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3aa3ad35ddbb/vmlinux-ba16c1cf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cdae0ed7d4a3/bzImage-ba16c1cf.xz

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

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

write to 0xffff88810fc6900c of 4 bytes by task 26582 on cpu 1:
aio_complete fs/aio.c:1168 [inline]
iocb_put+0x160/0x680 fs/aio.c:1215
io_submit_one+0xb26/0x1240 fs/aio.c:2061
__do_sys_io_submit fs/aio.c:2117 [inline]
__se_sys_io_submit+0xf5/0x280 fs/aio.c:2087
__x64_sys_io_submit+0x43/0x50 fs/aio.c:2087
x64_sys_call+0x2a7d/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:210
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88810fc6900c of 4 bytes by task 26580 on cpu 0:
aio_read_events_ring fs/aio.c:1244 [inline]
aio_read_events+0x8d/0x3c0 fs/aio.c:1304
read_events fs/aio.c:1340 [inline]
do_io_getevents+0x129/0x400 fs/aio.c:2236
__do_sys_io_getevents fs/aio.c:2269 [inline]
__se_sys_io_getevents fs/aio.c:2257 [inline]
__x64_sys_io_getevents+0xca/0x190 fs/aio.c:2257
x64_sys_call+0x1e8c/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:209
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x0000001e -> 0x00000029

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 26580 Comm: syz-executor.3 Tainted: G W 6.9.0-rc7-syzkaller-00188-gba16c1cf11c9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
==================================================================


---
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
Reply all
Reply to author
Forward
0 new messages