KCSAN: data-race in recursively_mark_NOTATTACHED / usb_submit_urb (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 09162bc3 Linux 5.10-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=151d86a6500000
kernel config: https://syzkaller.appspot.com/x/.config?x=e0bbcd06922dbd46
dashboard link: https://syzkaller.appspot.com/bug?extid=9b960064885237bf16a3
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [ero...@de.adit-jv.com gre...@linuxfoundation.org linux-...@vger.kernel.org linu...@vger.kernel.org one...@suse.com st...@rowland.harvard.edu]

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+9b9600...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in recursively_mark_NOTATTACHED / usb_submit_urb

write to 0xffff88812c317818 of 4 bytes by task 56 on cpu 1:
recursively_mark_NOTATTACHED+0x1af/0x1d0 drivers/usb/core/hub.c:2012
usb_set_device_state drivers/usb/core/hub.c:2070 [inline]
usb_disconnect+0x60/0x4b0 drivers/usb/core/hub.c:2198
hub_port_connect drivers/usb/core/hub.c:5073 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5362 [inline]
port_event drivers/usb/core/hub.c:5508 [inline]
hub_event+0x13bb/0x2b60 drivers/usb/core/hub.c:5590
process_one_work+0x3e1/0x950 kernel/workqueue.c:2272
worker_thread+0x635/0xb90 kernel/workqueue.c:2418
kthread+0x1fa/0x220 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

read to 0xffff88812c317818 of 4 bytes by interrupt on cpu 0:
usb_submit_urb+0xb0/0xbc0 drivers/usb/core/urb.c:383
ath9k_hif_usb_reg_in_cb+0x2c9/0x350 drivers/net/wireless/ath/ath9k/hif_usb.c:756
__usb_hcd_giveback_urb+0x219/0x290 drivers/usb/core/hcd.c:1650
usb_hcd_giveback_urb+0xae/0x210 drivers/usb/core/hcd.c:1716
dummy_timer+0x4d3/0x2390 drivers/usb/gadget/udc/dummy_hcd.c:1967
call_timer_fn+0x2e/0x240 kernel/time/timer.c:1410
expire_timers+0x116/0x260 kernel/time/timer.c:1455
__run_timers+0x328/0x3c0 kernel/time/timer.c:1747
run_timer_softirq+0x19/0x30 kernel/time/timer.c:1760
__do_softirq+0x12c/0x2b1 kernel/softirq.c:298
asm_call_irq_on_stack+0xf/0x20
__run_on_irqstack arch/x86/include/asm/irq_stack.h:26 [inline]
run_on_irqstack_cond arch/x86/include/asm/irq_stack.h:77 [inline]
do_softirq_own_stack+0x32/0x40 arch/x86/kernel/irq_64.c:77
invoke_softirq kernel/softirq.c:393 [inline]
__irq_exit_rcu+0xb2/0xc0 kernel/softirq.c:423
sysvec_apic_timer_interrupt+0x74/0x90 arch/x86/kernel/apic/apic.c:1091
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:631
devkmsg_read+0x4ab/0x580 kernel/printk/printk.c:801
vfs_read+0x154/0x5c0 fs/read_write.c:494
ksys_read+0xce/0x180 fs/read_write.c:634
__do_sys_read fs/read_write.c:644 [inline]
__se_sys_read fs/read_write.c:642 [inline]
__x64_sys_read+0x3e/0x50 fs/read_write.c:642
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 4870 Comm: systemd-journal Not tainted 5.10.0-rc4-syzkaller #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]

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