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

1 view
Skip to first unread message

syzbot

unread,
Feb 29, 2024, 9:13:29 PMFeb 29
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 805d849d7c3c Merge tag 'acpi-6.8-rc7' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11264aa2180000
kernel config: https://syzkaller.appspot.com/x/.config?x=53006d590acdf777
dashboard link: https://syzkaller.appspot.com/bug?extid=b5c57554a4fbc1aa6969
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/c550e093323d/disk-805d849d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/42cd67389a8e/vmlinux-805d849d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/90500a18c974/bzImage-805d849d.xz

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

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

write to 0xffff88811226d00c of 4 bytes by task 29987 on cpu 1:
aio_complete fs/aio.c:1164 [inline]
iocb_put+0x160/0x670 fs/aio.c:1211
io_submit_one+0xb47/0x1250 fs/aio.c:2057
__do_sys_io_submit fs/aio.c:2113 [inline]
__se_sys_io_submit+0xf5/0x280 fs/aio.c:2083
__x64_sys_io_submit+0x43/0x50 fs/aio.c:2083
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+0x63/0x6b

read to 0xffff88811226d00c of 4 bytes by task 29988 on cpu 0:
aio_read_events_ring fs/aio.c:1240 [inline]
aio_read_events+0x8d/0x3b0 fs/aio.c:1300
read_events fs/aio.c:1336 [inline]
do_io_getevents+0x129/0x3f0 fs/aio.c:2232
__do_sys_io_getevents fs/aio.c:2265 [inline]
__se_sys_io_getevents fs/aio.c:2253 [inline]
__x64_sys_io_getevents+0xca/0x190 fs/aio.c:2253
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+0x63/0x6b

value changed: 0x00000000 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 29988 Comm: syz-executor.4 Not tainted 6.8.0-rc6-syzkaller-00037-g805d849d7c3c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/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

syzbot

unread,
Apr 4, 2024, 10:13:21 PMApr 4
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages