KCSAN: data-race in io_uring_create / io_uring_create

11 views
Skip to first unread message

syzbot

unread,
Dec 7, 2020, 7:03:11 AM12/7/20
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: a349e4c6 Merge tag 'xfs-5.10-fixes-7' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11f6e0a5500000
kernel config: https://syzkaller.appspot.com/x/.config?x=89a86a84f1254241
dashboard link: https://syzkaller.appspot.com/bug?extid=e73ecce86fb5d112950d
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [ax...@kernel.dk io-u...@vger.kernel.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.

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

==================================================================
BUG: KCSAN: data-race in io_uring_create / io_uring_create

read-write to 0xffff88810633aa48 of 8 bytes by task 15118 on cpu 1:
io_account_mem fs/io_uring.c:7909 [inline]
io_uring_create+0xce4/0x1ef0 fs/io_uring.c:9330
io_uring_setup fs/io_uring.c:9411 [inline]
__do_sys_io_uring_setup fs/io_uring.c:9417 [inline]
__se_sys_io_uring_setup fs/io_uring.c:9414 [inline]
__x64_sys_io_uring_setup+0xe1/0x120 fs/io_uring.c:9414
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

read-write to 0xffff88810633aa48 of 8 bytes by task 15106 on cpu 0:
io_account_mem fs/io_uring.c:7909 [inline]
io_uring_create+0xce4/0x1ef0 fs/io_uring.c:9330
io_uring_setup fs/io_uring.c:9411 [inline]
__do_sys_io_uring_setup fs/io_uring.c:9417 [inline]
__se_sys_io_uring_setup fs/io_uring.c:9414 [inline]
__x64_sys_io_uring_setup+0xe1/0x120 fs/io_uring.c:9414
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 15106 Comm: syz-executor.0 Not tainted 5.10.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 15106 Comm: syz-executor.0 Not tainted 5.10.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x116/0x15d lib/dump_stack.c:118
panic+0x1e7/0x5fa kernel/panic.c:231
kcsan_report+0x67b/0x680 kernel/kcsan/report.c:634
kcsan_setup_watchpoint+0x46a/0x4d0 kernel/kcsan/core.c:568
io_account_mem fs/io_uring.c:7909 [inline]
io_uring_create+0xce4/0x1ef0 fs/io_uring.c:9330
io_uring_setup fs/io_uring.c:9411 [inline]
__do_sys_io_uring_setup fs/io_uring.c:9417 [inline]
__se_sys_io_uring_setup fs/io_uring.c:9414 [inline]
__x64_sys_io_uring_setup+0xe1/0x120 fs/io_uring.c:9414
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45deb9
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fa307e30bf8 EFLAGS: 00000206 ORIG_RAX: 00000000000001a9
RAX: ffffffffffffffda RBX: 0000000020000000 RCX: 000000000045deb9
RDX: 0000000020b7f000 RSI: 0000000020000000 RDI: 00000000000017ee
RBP: 000000000118bf78 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000080 R11: 0000000000000206 R12: 0000000020b7f000
R13: 0000000020aa5000 R14: 0000000000000000 R15: 0000000020000080
Kernel Offset: disabled
Rebooting in 86400 seconds..


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

syzbot

unread,
Dec 27, 2020, 2:41:11 PM12/27/20
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