Hello,
syzbot found the following issue on:
HEAD commit: d98fd109f827 Linux 5.15.172
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16bfeb5f980000
kernel config:
https://syzkaller.appspot.com/x/.config?x=106da063d1125aa0
dashboard link:
https://syzkaller.appspot.com/bug?extid=15f90be5f5a9bd9ce26e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/d480511ac07d/disk-d98fd109.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/743b2602e9fd/vmlinux-d98fd109.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/c93fe25414b0/bzImage-d98fd109.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+15f90b...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1108 at drivers/net/wireless/ath/ath6kl/bmi.c:90 ath6kl_bmi_get_target_info+0x426/0x570
Modules linked in:
CPU: 0 PID: 1108 Comm: kworker/0:2 Not tainted 5.15.172-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: usb_hub_wq hub_event
RIP: 0010:ath6kl_bmi_get_target_info+0x426/0x570 drivers/net/wireless/ath/ath6kl/bmi.c:90
Code: b6 04 30 84 c0 0f 85 38 01 00 00 48 8b 44 24 08 8b 30 48 c7 c7 40 4a 18 8b 89 da e8 24 1f fe ff e9 14 fe ff ff e8 9a c8 b6 fb <0f> 0b bb ea ff ff ff e9 03 fe ff ff e8 89 c8 b6 fb 31 db e9 f7 fd
RSP: 0018:ffffc900047aebe0 EFLAGS: 00010287
RAX: ffffffff85c9ab06 RBX: 0000000000000000 RCX: 0000000000100000
RDX: ffffc90010e39000 RSI: 0000000000022b8d RDI: 0000000000022b8e
RBP: ffffc900047aecb0 R08: ffffffff85c9aa63 R09: fffffbfff20ec82f
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc900047aed64
R13: ffff888074dc0da0 R14: dffffc0000000000 R15: 1ffff920008f5d84
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000203f5030 CR3: 0000000074e7d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ath6kl_core_init+0x1df/0x1120 drivers/net/wireless/ath/ath6kl/core.c:101
ath6kl_usb_probe+0x11e9/0x12e0 drivers/net/wireless/ath/ath6kl/usb.c:1160
usb_probe_interface+0x5c0/0xaf0 drivers/usb/core/driver.c:396
really_probe+0x24e/0xb60 drivers/base/dd.c:595
__driver_probe_device+0x1a2/0x3d0 drivers/base/dd.c:755
driver_probe_device+0x50/0x420 drivers/base/dd.c:785
__device_attach_driver+0x2b9/0x500 drivers/base/dd.c:907
bus_for_each_drv+0x183/0x200 drivers/base/bus.c:429
__device_attach+0x359/0x570 drivers/base/dd.c:979
bus_probe_device+0xba/0x1e0 drivers/base/bus.c:489
device_add+0xb48/0xfd0 drivers/base/core.c:3412
usb_set_configuration+0x19dd/0x2020 drivers/usb/core/message.c:2165
usb_generic_driver_probe+0x84/0x140 drivers/usb/core/generic.c:238
usb_probe_device+0x130/0x260 drivers/usb/core/driver.c:293
really_probe+0x24e/0xb60 drivers/base/dd.c:595
__driver_probe_device+0x1a2/0x3d0 drivers/base/dd.c:755
driver_probe_device+0x50/0x420 drivers/base/dd.c:785
__device_attach_driver+0x2b9/0x500 drivers/base/dd.c:907
bus_for_each_drv+0x183/0x200 drivers/base/bus.c:429
__device_attach+0x359/0x570 drivers/base/dd.c:979
bus_probe_device+0xba/0x1e0 drivers/base/bus.c:489
device_add+0xb48/0xfd0 drivers/base/core.c:3412
usb_new_device+0xc17/0x18e0 drivers/usb/core/hub.c:2593
hub_port_connect drivers/usb/core/hub.c:5455 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5595 [inline]
port_event drivers/usb/core/hub.c:5741 [inline]
hub_event+0x2cdf/0x54c0 drivers/usb/core/hub.c:5823
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
---
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