[moderation] [fs?] WARNING in comedi_release_hardware_device (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8be0c877fb3b thunderbolt: make tb_bus_type const
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=1541f3e9e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1dd225f9d04a5286
dashboard link: https://syzkaller.appspot.com/bug?extid=b7d15d422fa5f76e2b02
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org linux-...@vger.kernel.org linu...@vger.kernel.org raf...@kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/831abeb4b7c5/disk-8be0c877.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9d0229b6f3c5/vmlinux-8be0c877.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a89e578f1fb6/bzImage-8be0c877.xz

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

vmk80xx 6-1:0.0: driver 'vmk80xx' failed to auto-configure device.
------------[ cut here ]------------
sysfs group 'power' not found for kobject 'comedi0'
WARNING: CPU: 0 PID: 4842 at fs/sysfs/group.c:282 sysfs_remove_group+0x12a/0x170 fs/sysfs/group.c:282
Modules linked in:
CPU: 0 PID: 4842 Comm: kworker/0:5 Not tainted 6.7.0-rc5-syzkaller-g8be0c877fb3b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: usb_hub_wq hub_event
RIP: 0010:sysfs_remove_group+0x12a/0x170 fs/sysfs/group.c:282
Code: 48 89 d9 49 8b 14 24 48 b8 00 00 00 00 00 fc ff df 48 c1 e9 03 80 3c 01 00 75 37 48 8b 33 48 c7 c7 60 1b 98 86 e8 86 f3 50 ff <0f> 0b eb 98 e8 5d 3f d5 ff e9 01 ff ff ff 48 89 df e8 50 3f d5 ff
RSP: 0018:ffffc9000d8aef60 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffffff86c984a0 RCX: ffffc9000e309000
RDX: 0000000000040000 RSI: ffffffff811733c6 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000506360 R12: ffff88811bdf8000
R13: ffffffff86c98a40 R14: dffffc0000000000 R15: ffff88811c46b078
FS: 0000000000000000(0000) GS:ffff8881f6600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f58907e8000 CR3: 000000013a80c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
dpm_sysfs_remove+0x9d/0xb0 drivers/base/power/sysfs.c:837
device_del+0x1a8/0xa50 drivers/base/core.c:3789
device_unregister+0x1d/0xc0 drivers/base/core.c:3855
device_destroy+0x9a/0xd0 drivers/base/core.c:4414
comedi_free_board_dev drivers/comedi/comedi_fops.c:611 [inline]
comedi_free_board_dev drivers/comedi/comedi_fops.c:606 [inline]
comedi_release_hardware_device+0x196/0x210 drivers/comedi/comedi_fops.c:3291
comedi_auto_config+0x1f2/0x440 drivers/comedi/drivers.c:1076
usb_probe_interface+0x307/0x930 drivers/usb/core/driver.c:399
call_driver_probe drivers/base/dd.c:579 [inline]
really_probe+0x234/0xc90 drivers/base/dd.c:658
__driver_probe_device+0x1de/0x4b0 drivers/base/dd.c:800
driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:830
__device_attach_driver+0x1d4/0x300 drivers/base/dd.c:958
bus_for_each_drv+0x157/0x1d0 drivers/base/bus.c:457
__device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030
bus_probe_device+0x17c/0x1c0 drivers/base/bus.c:532
device_add+0x117e/0x1aa0 drivers/base/core.c:3625
usb_set_configuration+0x10cb/0x1c40 drivers/usb/core/message.c:2207
usb_generic_driver_probe+0xad/0x110 drivers/usb/core/generic.c:254
usb_probe_device+0xec/0x350 drivers/usb/core/driver.c:294
call_driver_probe drivers/base/dd.c:579 [inline]
really_probe+0x234/0xc90 drivers/base/dd.c:658
__driver_probe_device+0x1de/0x4b0 drivers/base/dd.c:800
driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:830
__device_attach_driver+0x1d4/0x300 drivers/base/dd.c:958
bus_for_each_drv+0x157/0x1d0 drivers/base/bus.c:457
__device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030
bus_probe_device+0x17c/0x1c0 drivers/base/bus.c:532
device_add+0x117e/0x1aa0 drivers/base/core.c:3625
usb_new_device+0xd80/0x19f0 drivers/usb/core/hub.c:2596
hub_port_connect drivers/usb/core/hub.c:5465 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5605 [inline]
port_event drivers/usb/core/hub.c:5765 [inline]
hub_event+0x2e62/0x4f40 drivers/usb/core/hub.c:5847
process_one_work+0x884/0x15c0 kernel/workqueue.c:2627
process_scheduled_works kernel/workqueue.c:2700 [inline]
worker_thread+0x8b9/0x1290 kernel/workqueue.c:2781
kthread+0x33c/0x440 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
</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

[syzbot]

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