[moderation] [kernel?] KCSAN: data-race in do_mq_timedreceive / do_mq_timedsend (2)

2 views
Skip to first unread message

syzbot

unread,
Dec 7, 2024, 2:40:28 PM12/7/24
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b5f217084ab3 Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16fcc4df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ff022027cd3a0001
dashboard link: https://syzkaller.appspot.com/bug?extid=7286d33689a8e59c0546
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [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/70eb04da8ec7/disk-b5f21708.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/79eb071392d1/vmlinux-b5f21708.xz
kernel image: https://storage.googleapis.com/syzbot-assets/96958c32e31c/bzImage-b5f21708.xz

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

==================================================================
BUG: KCSAN: data-race in do_mq_timedreceive / do_mq_timedsend

write to 0xffff88811473e450 of 8 bytes by task 6628 on cpu 0:
do_mq_timedsend+0x30e/0x680 ipc/mqueue.c:1123
__do_sys_mq_timedsend ipc/mqueue.c:1269 [inline]
__se_sys_mq_timedsend ipc/mqueue.c:1258 [inline]
__x64_sys_mq_timedsend+0xca/0x150 ipc/mqueue.c:1258
x64_sys_call+0x2a68/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:243
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88811473e450 of 8 bytes by task 6631 on cpu 1:
do_mq_timedreceive+0x205/0x6d0 ipc/mqueue.c:1208
__do_sys_mq_timedreceive ipc/mqueue.c:1283 [inline]
__se_sys_mq_timedreceive ipc/mqueue.c:1272 [inline]
__x64_sys_mq_timedreceive+0xca/0x150 ipc/mqueue.c:1272
x64_sys_call+0x18f1/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:244
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x0000000000000000 -> 0xffff888117a4b980

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 6631 Comm: syz.1.838 Not tainted 6.13.0-rc1-syzkaller-00316-gb5f217084ab3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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,
Feb 12, 2025, 1:36:13 PM2/12/25
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