WARNING in ath9k_hif_usb_alloc_urbs/usb_submit_urb

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: b3a9e3b9 Linux 5.8-rc1
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=134f82b9100000
kernel config: https://syzkaller.appspot.com/x/.config?x=517257c0c3ef89af
dashboard link: https://syzkaller.appspot.com/bug?extid=d625c772c7814faabef9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1695e621100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1393f8b9100000

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

WARNING: CPU: 1 PID: 57 at drivers/usb/core/urb.c:478 usb_submit_urb+0x1188/0x1460 drivers/usb/core/urb.c:478
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 57 Comm: kworker/1:2 Not tainted 5.8.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events request_firmware_work_func
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0xf6/0x16e lib/dump_stack.c:118
panic+0x2aa/0x6e1 kernel/panic.c:231
__warn.cold+0x2f/0x35 kernel/panic.c:600
report_bug+0x271/0x2f0 lib/bug.c:198
exc_invalid_op+0x1e4/0x370 arch/x86/kernel/traps.c:235
asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:563
RIP: 0010:usb_submit_urb+0x1188/0x1460 drivers/usb/core/urb.c:478
Code: 4d 85 ed 74 46 e8 48 96 d0 fd 4c 89 f7 e8 a0 02 16 ff 41 89 d8 44 89 e1 4c 89 ea 48 89 c6 48 c7 c7 80 b3 3d 86 e8 3a ac a4 fd <0f> 0b e9 20 f4 ff ff e8 1c 96 d0 fd 0f 1f 44 00 00 e8 12 96 d0 fd
RSP: 0018:ffff8881d8ab7b50 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff81298423 RDI: ffffed103b156f5c
RBP: ffff8881c8c7e450 R08: ffff8881d8aa1900 R09: ffffed103b665ea2
R10: ffff8881db32f50f R11: ffffed103b665ea1 R12: 0000000000000003
R13: ffff8881c700adc8 R14: ffff8881d8e250a0 R15: ffff8881d54c7700
ath9k_hif_usb_alloc_rx_urbs drivers/net/wireless/ath/ath9k/hif_usb.c:880 [inline]
ath9k_hif_usb_alloc_urbs+0x7be/0x1050 drivers/net/wireless/ath/ath9k/hif_usb.c:991
ath9k_hif_usb_dev_init drivers/net/wireless/ath/ath9k/hif_usb.c:1081 [inline]
ath9k_hif_usb_firmware_cb+0x148/0x510 drivers/net/wireless/ath/ath9k/hif_usb.c:1214
request_firmware_work_func+0x126/0x242 drivers/base/firmware_loader/main.c:1001
process_one_work+0x965/0x1620 kernel/workqueue.c:2269
worker_thread+0x96/0xe10 kernel/workqueue.c:2415
kthread+0x352/0x460 kernel/kthread.c:291
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
Kernel Offset: disabled


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches

[syzbot]

syzbot suspects this issue was fixed by commit:

commit 16ef02bad239f11f322df8425d302be62f0443ce
Author: Fedor Pchelkin <pche...@ispras.ru>
Date: Sat Oct 8 21:15:32 2022 +0000

wifi: ath9k: verify the expected usb_endpoints are present

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=153e9c11480000
start commit: 55be6084c8e0 Merge tag 'timers-core-2022-10-05' of git://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=df75278aabf0681a
dashboard link: https://syzkaller.appspot.com/bug?extid=d625c772c7814faabef9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=138d8cc2880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b2dc3c880000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: wifi: ath9k: verify the expected usb_endpoints are present

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.