[moderation] [afs?] [net?] KCSAN: data-race in rxrpc_send_data / rxrpc_transmit_some_data

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3a8a670eeeaa Merge tag 'net-next-6.5' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16a56440a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=bb89d2637be0215c
dashboard link: https://syzkaller.appspot.com/bug?extid=10a8b2c396f558269522
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [da...@davemloft.net dhow...@redhat.com edum...@google.com ku...@kernel.org linu...@lists.infradead.org linux-...@vger.kernel.org linux-...@vger.kernel.org marc....@auristor.com net...@vger.kernel.org pab...@redhat.com]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f56e8be6c07b/disk-3a8a670e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b2275e88e175/vmlinux-3a8a670e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e89ddbca531b/bzImage-3a8a670e.xz

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

==================================================================
BUG: KCSAN: data-race in rxrpc_send_data / rxrpc_transmit_some_data

write to 0xffff888109178274 of 4 bytes by task 20953 on cpu 0:
rxrpc_decant_prepared_tx net/rxrpc/call_event.c:320 [inline]
rxrpc_transmit_some_data+0x37d/0x600 net/rxrpc/call_event.c:350
rxrpc_input_call_event+0x564/0x1220 net/rxrpc/call_event.c:464
rxrpc_io_thread+0x307/0x1d80 net/rxrpc/io_thread.c:461
kthread+0x1d7/0x210 kernel/kthread.c:389
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

read to 0xffff888109178274 of 4 bytes by task 20952 on cpu 1:
rxrpc_send_data+0x951/0x1960 net/rxrpc/sendmsg.c:401
rxrpc_do_sendmsg+0xba8/0xc40 net/rxrpc/sendmsg.c:726
rxrpc_sendmsg+0x413/0x520 net/rxrpc/af_rxrpc.c:581
sock_sendmsg_nosec net/socket.c:725 [inline]
sock_sendmsg net/socket.c:748 [inline]
____sys_sendmsg+0x37c/0x4d0 net/socket.c:2494
___sys_sendmsg net/socket.c:2548 [inline]
__sys_sendmsg+0x1e9/0x270 net/socket.c:2577
__do_sys_sendmsg net/socket.c:2586 [inline]
__se_sys_sendmsg net/socket.c:2584 [inline]
__x64_sys_sendmsg+0x46/0x50 net/socket.c:2584
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

value changed: 0x00000000 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 20952 Comm: syz-executor.2 Not tainted 6.4.0-syzkaller-04247-g3a8a670eeeaa #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.