[moderation] [tipc?] KCSAN: data-race in tipc_poll / tipc_sk_proto_rcv (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8ffd015db85f Linux 6.15-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1685b398580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f723126dfc2a8a53
dashboard link: https://syzkaller.appspot.com/bug?extid=e5303be9ad4d4ff7911f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [da...@davemloft.net edum...@google.com ho...@kernel.org jma...@redhat.com ku...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org pab...@redhat.com tipc-di...@lists.sourceforge.net]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/913870d2b804/disk-8ffd015d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ccfc14b57099/vmlinux-8ffd015d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/61a5e4adfd43/bzImage-8ffd015d.xz

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

==================================================================
BUG: KCSAN: data-race in tipc_poll / tipc_sk_proto_rcv

read-write to 0xffff888103685786 of 2 bytes by task 8807 on cpu 0:
tipc_sk_conn_proto_rcv net/tipc/socket.c:1367 [inline]
tipc_sk_proto_rcv+0x672/0xb70 net/tipc/socket.c:2156
tipc_sk_filter_rcv+0x18ed/0x1a20 net/tipc/socket.c:2350
tipc_sk_enqueue net/tipc/socket.c:2443 [inline]
tipc_sk_rcv+0x48b/0x1020 net/tipc/socket.c:2495
tipc_node_xmit+0x234/0x8b0 net/tipc/node.c:1701
tipc_node_xmit_skb+0x99/0xd0 net/tipc/node.c:1766
tipc_sk_send_ack+0x265/0x280 net/tipc/socket.c:1824
tipc_recvstream+0x3b2/0x7e0 net/tipc/socket.c:2093
sock_recvmsg_nosec net/socket.c:1017 [inline]
sock_recvmsg+0x13f/0x170 net/socket.c:1039
____sys_recvmsg+0xfb/0x290 net/socket.c:2786
___sys_recvmsg net/socket.c:2828 [inline]
__sys_recvmsg+0x1c7/0x270 net/socket.c:2861
__do_sys_recvmsg net/socket.c:2867 [inline]
__se_sys_recvmsg net/socket.c:2864 [inline]
__x64_sys_recvmsg+0x46/0x50 net/socket.c:2864
x64_sys_call+0xc6d/0x2e10 arch/x86/include/generated/asm/syscalls_64.h:48
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888103685786 of 2 bytes by task 8809 on cpu 1:
tsk_conn_cong net/tipc/socket.c:222 [inline]
tipc_poll+0x1f6/0x360 net/tipc/socket.c:806
sock_poll+0x22d/0x250 net/socket.c:1379
vfs_poll include/linux/poll.h:82 [inline]
__io_arm_poll_handler+0x1e5/0xd40 io_uring/poll.c:583
io_arm_poll_handler+0x4b0/0x5f0 io_uring/poll.c:708
io_queue_async+0x8a/0x460 io_uring/io_uring.c:1947
io_queue_sqe io_uring/io_uring.c:1976 [inline]
io_submit_sqe io_uring/io_uring.c:2225 [inline]
io_submit_sqes+0x9f2/0x1050 io_uring/io_uring.c:2342
__do_sys_io_uring_enter io_uring/io_uring.c:3402 [inline]
__se_sys_io_uring_enter+0x1ce/0x1c00 io_uring/io_uring.c:3336
__x64_sys_io_uring_enter+0x78/0x90 io_uring/io_uring.c:3336
x64_sys_call+0x26cb/0x2e10 arch/x86/include/generated/asm/syscalls_64.h:427
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x020a -> 0x0188

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 8809 Comm: syz.1.1674 Not tainted 6.15.0-rc2-syzkaller #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
==================================================================


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

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