KCSAN: data-race in rxrpc_activate_one_channel / rxrpc_connect_call

12 views
Skip to first unread message

syzbot

unread,
Mar 19, 2022, 2:17:18 PM3/19/22
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: aad611a868d1 Merge tag 'perf-tools-fixes-for-v5.17-2022-03..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=110184d5700000
kernel config: https://syzkaller.appspot.com/x/.config?x=5f8eb792c7b91c8f
dashboard link: https://syzkaller.appspot.com/bug?extid=71ad20d9b91fc9a21fe2
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [da...@davemloft.net dhow...@redhat.com ku...@kernel.org linu...@lists.infradead.org linux-...@vger.kernel.org marc....@auristor.com net...@vger.kernel.org]

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+71ad20...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in rxrpc_activate_one_channel / rxrpc_connect_call

write to 0xffff8881447cdd50 of 4 bytes by task 20595 on cpu 0:
rxrpc_activate_one_channel+0x210/0x3f0 net/rxrpc/conn_client.c:539
rxrpc_activate_channels_locked+0x265/0x2c0 net/rxrpc/conn_client.c:614
rxrpc_activate_channels net/rxrpc/conn_client.c:631 [inline]
rxrpc_wait_for_channel+0x18a/0x4a0 net/rxrpc/conn_client.c:657
rxrpc_connect_call+0x4a6/0xac0 net/rxrpc/conn_client.c:715
rxrpc_new_client_call+0x519/0x9b0 net/rxrpc/call_object.c:330
rxrpc_new_client_call_for_sendmsg net/rxrpc/sendmsg.c:605 [inline]
rxrpc_do_sendmsg+0x7b0/0xcf0 net/rxrpc/sendmsg.c:658
rxrpc_sendmsg+0x3d7/0x4c0 net/rxrpc/af_rxrpc.c:561
sock_sendmsg_nosec net/socket.c:705 [inline]
sock_sendmsg net/socket.c:725 [inline]
____sys_sendmsg+0x39a/0x510 net/socket.c:2413
___sys_sendmsg net/socket.c:2467 [inline]
__sys_sendmmsg+0x267/0x4c0 net/socket.c:2553
__do_sys_sendmmsg net/socket.c:2582 [inline]
__se_sys_sendmmsg net/socket.c:2579 [inline]
__x64_sys_sendmmsg+0x53/0x60 net/socket.c:2579
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff8881447cdd50 of 4 bytes by task 20596 on cpu 1:
rxrpc_connect_call+0x47b/0xac0 net/rxrpc/conn_client.c:714
rxrpc_new_client_call+0x519/0x9b0 net/rxrpc/call_object.c:330
rxrpc_new_client_call_for_sendmsg net/rxrpc/sendmsg.c:605 [inline]
rxrpc_do_sendmsg+0x7b0/0xcf0 net/rxrpc/sendmsg.c:658
rxrpc_sendmsg+0x3d7/0x4c0 net/rxrpc/af_rxrpc.c:561
sock_sendmsg_nosec net/socket.c:705 [inline]
sock_sendmsg net/socket.c:725 [inline]
____sys_sendmsg+0x39a/0x510 net/socket.c:2413
___sys_sendmsg net/socket.c:2467 [inline]
__sys_sendmmsg+0x267/0x4c0 net/socket.c:2553
__do_sys_sendmmsg net/socket.c:2582 [inline]
__se_sys_sendmmsg net/socket.c:2579 [inline]
__x64_sys_sendmmsg+0x53/0x60 net/socket.c:2579
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x00000001 -> 0x00000002

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 20596 Comm: syz-executor.3 Not tainted 5.17.0-rc7-syzkaller-00235-gaad611a868d1-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


---
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,
Apr 17, 2022, 10:33:16 AM4/17/22
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