[moderation] [usb?] KCSAN: data-race in rh_port_connect / vhci_hub_control

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fca7526b7d89 drm/tests/drm_buddy: fix build failure on 32-..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1554a072180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7507056e4ee79a
dashboard link: https://syzkaller.appspot.com/bug?extid=075794fc7e3c9f087790
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org i...@zenithal.me linux-...@vger.kernel.org linu...@vger.kernel.org sh...@kernel.org valentin...@gmail.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c63152c2a9c6/disk-fca7526b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6f039180eecf/vmlinux-fca7526b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0340d7a9d91f/bzImage-fca7526b.xz

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

==================================================================
BUG: KCSAN: data-race in rh_port_connect / vhci_hub_control

write to 0xffff8881014cf278 of 4 bytes by task 542 on cpu 1:
rh_port_connect+0xbd/0xf0 drivers/usb/usbip/vhci_hcd.c:180
attach_store+0x609/0x6b0 drivers/usb/usbip/vhci_sysfs.c:436
dev_attr_store+0x44/0x60 drivers/base/core.c:2380
sysfs_kf_write+0xaa/0xc0 fs/sysfs/file.c:136
kernfs_fop_write_iter+0x1ca/0x2b0 fs/kernfs/file.c:334
call_write_iter include/linux/fs.h:2085 [inline]
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0x760/0x8d0 fs/read_write.c:590
ksys_write+0xeb/0x1a0 fs/read_write.c:643
__do_sys_write fs/read_write.c:655 [inline]
__se_sys_write fs/read_write.c:652 [inline]
__x64_sys_write+0x42/0x50 fs/read_write.c:652
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff8881014cf278 of 4 bytes by task 3326 on cpu 0:
vhci_hub_control+0xd68/0xdc0 drivers/usb/usbip/vhci_hcd.c:657
rh_call_control drivers/usb/core/hcd.c:658 [inline]
rh_urb_enqueue drivers/usb/core/hcd.c:823 [inline]
usb_hcd_submit_urb+0xca2/0x14c0 drivers/usb/core/hcd.c:1531
usb_submit_urb+0xb0e/0xbc0 drivers/usb/core/urb.c:581
usb_start_wait_urb+0x91/0x190 drivers/usb/core/message.c:59
usb_internal_control_msg drivers/usb/core/message.c:103 [inline]
usb_control_msg+0x182/0x240 drivers/usb/core/message.c:154
get_port_status drivers/usb/core/hub.c:604 [inline]
hub_ext_port_status+0xb4/0x380 drivers/usb/core/hub.c:621
usb_hub_port_status drivers/usb/core/hub.c:643 [inline]
hub_port_debounce+0x1a8/0x210 drivers/usb/core/hub.c:4619
hub_port_debounce_be_stable drivers/usb/core/hub.h:181 [inline]
hub_port_connect drivers/usb/core/hub.c:5335 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5623 [inline]
port_event drivers/usb/core/hub.c:5783 [inline]
hub_event+0x1518/0x2920 drivers/usb/core/hub.c:5865
process_one_work kernel/workqueue.c:2633 [inline]
process_scheduled_works+0x5b8/0xa40 kernel/workqueue.c:2706
worker_thread+0x525/0x730 kernel/workqueue.c:2787
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

value changed: 0x00000700 -> 0x00010701

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 3326 Comm: kworker/0:13 Not tainted 6.8.0-rc5-syzkaller-00002-gfca7526b7d89 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: usb_hub_wq hub_event
==================================================================


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