[moderation] [usb?] KCSAN: data-race in mon_reader_add / usb_hcd_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e5eb28f6d1af Merge tag 'mm-nonmm-stable-2024-03-14-09-36' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16a1bea5180000
kernel config: https://syzkaller.appspot.com/x/.config?x=61230552cbbfeeb1
dashboard link: https://syzkaller.appspot.com/bug?extid=b058302c4be61d8c6bf2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org linu...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2042ccf04ea5/disk-e5eb28f6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/827a201c619a/vmlinux-e5eb28f6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/824f31b68ffa/bzImage-e5eb28f6.xz

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

==================================================================
BUG: KCSAN: data-race in mon_reader_add / usb_hcd_submit_urb

write to 0xffff888101eac088 of 4 bytes by task 14887 on cpu 1:
mon_reader_add+0xc7/0x1f0 drivers/usb/mon/mon_main.c:47
mon_bin_open+0x32b/0x3b0 drivers/usb/mon/mon_bin.c:720
chrdev_open+0x323/0x3a0 fs/char_dev.c:414
do_dentry_open+0x63c/0xbe0 fs/open.c:955
vfs_open+0x4a/0x60 fs/open.c:1089
do_open fs/namei.c:3642 [inline]
path_openat+0x18ba/0x1d80 fs/namei.c:3799
do_filp_open+0xf7/0x200 fs/namei.c:3826
do_sys_openat2+0xab/0x120 fs/open.c:1406
do_sys_open fs/open.c:1421 [inline]
__do_sys_openat fs/open.c:1437 [inline]
__se_sys_openat fs/open.c:1432 [inline]
__x64_sys_openat+0xf3/0x120 fs/open.c:1432
do_syscall_64+0xd3/0x1d0
entry_SYSCALL_64_after_hwframe+0x6d/0x75

read to 0xffff888101eac088 of 4 bytes by task 5637 on cpu 0:
usbmon_urb_submit include/linux/usb/hcd.h:723 [inline]
usb_hcd_submit_urb+0x86/0x1510 drivers/usb/core/hcd.c:1520
usb_submit_urb+0xb12/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]
port_event drivers/usb/core/hub.c:5676 [inline]
hub_event+0x535/0x2900 drivers/usb/core/hub.c:5865
process_one_work kernel/workqueue.c:3254 [inline]
process_scheduled_works+0x465/0x990 kernel/workqueue.c:3335
worker_thread+0x526/0x730 kernel/workqueue.c:3416
kthread+0x1d1/0x210 kernel/kthread.c:388
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243

value changed: 0x00000000 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 5637 Comm: kworker/0:9 Tainted: G W 6.8.0-syzkaller-09791-ge5eb28f6d1af #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/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.