[moderation] [io-uring?] KCSAN: data-race in io_submit_sqes / io_uring_poll (6)

0 views
Skip to first unread message

syzbot

unread,
Dec 10, 2023, 7:07:31 PM12/10/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 1b907d050735 Merge tag '6.7-rc-smb3-client-fixes-part2' of..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1170a5a7680000
kernel config: https://syzkaller.appspot.com/x/.config?x=1c4caf9f31b81308
dashboard link: https://syzkaller.appspot.com/bug?extid=0a9cd8e24b280b505a7b
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/b5fc887c0635/disk-1b907d05.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9e7fb6111fb0/vmlinux-1b907d05.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f40a896ae841/bzImage-1b907d05.xz

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

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

read-write to 0xffff888103e9f870 of 4 bytes by task 17125 on cpu 1:
io_get_sqe io_uring/io_uring.c:2385 [inline]
io_submit_sqes+0x242/0x1060 io_uring/io_uring.c:2436
__do_sys_io_uring_enter io_uring/io_uring.c:3709 [inline]
__se_sys_io_uring_enter+0x1eb/0x1b70 io_uring/io_uring.c:3643
__x64_sys_io_uring_enter+0x78/0x90 io_uring/io_uring.c:3643
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff888103e9f870 of 4 bytes by task 17248 on cpu 0:
io_sqring_full io_uring/io_uring.h:256 [inline]
io_uring_poll+0xcd/0x190 io_uring/io_uring.c:3016
vfs_poll include/linux/poll.h:88 [inline]
do_pollfd fs/select.c:873 [inline]
do_poll fs/select.c:921 [inline]
do_sys_poll+0x636/0xc00 fs/select.c:1015
__do_sys_ppoll fs/select.c:1121 [inline]
__se_sys_ppoll+0x1af/0x1f0 fs/select.c:1101
__x64_sys_ppoll+0x67/0x80 fs/select.c:1101
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00004fc0 -> 0x00004fc6

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 17248 Comm: syz-executor.5 Tainted: G W 6.6.0-syzkaller-16176-g1b907d050735 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/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

unread,
Dec 24, 2023, 7:08:13 PM12/24/23
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