[moderation] [fs?] WARNING in comedi_release_hardware_device

13 views
Skip to first unread message

syzbot

unread,
Sep 6, 2023, 4:47:02 AM9/6/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b84acc11b1c9 Merge tag 'fbdev-for-6.6-rc1' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=158edc67a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6dc9cc90b1ff4aa1
dashboard link: https://syzkaller.appspot.com/bug?extid=c33d335429d3b477ae2f
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 raf...@kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c536c0a856b9/disk-b84acc11.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f95c50b66e84/vmlinux-b84acc11.xz
kernel image: https://storage.googleapis.com/syzbot-assets/317b80e3689b/bzImage-b84acc11.xz

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

WARNING: CPU: 0 PID: 31325 at fs/sysfs/group.c:282 sysfs_remove_group+0x12a/0x170 fs/sysfs/group.c:282
Modules linked in:
CPU: 0 PID: 31325 Comm: kworker/0:3 Not tainted 6.5.0-syzkaller-10204-gb84acc11b1c9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/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 c0 1c 80 8a e8 f6 6a 38 ff <0f> 0b eb 98 e8 cd 03 c7 ff e9 01 ff ff ff 48 89 df e8 c0 03 c7 ff
RSP: 0018:ffffc9001643ef50 EFLAGS: 00010286

RAX: 0000000000000000 RBX: ffffffff8af213c0 RCX: ffffc90011935000
RDX: 0000000000040000 RSI: ffffffff814cc3e6 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 00000000005515e0 R12: ffff88801f4af000
R13: ffffffff8af21960 R14: dffffc0000000000 R15: ffff88801f09f078
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2ee23000 CR3: 000000007cbb1000 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:3786
device_unregister+0x1d/0xc0 drivers/base/core.c:3852
device_destroy+0x9a/0xd0 drivers/base/core.c:4411
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:1075
usb_probe_interface+0x307/0x930 drivers/usb/core/driver.c:396
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+0x1182/0x1ac0 drivers/base/core.c:3622
usb_set_configuration+0x10cb/0x1c40 drivers/usb/core/message.c:2207
usb_generic_driver_probe+0xca/0x130 drivers/usb/core/generic.c:238
usb_probe_device+0xda/0x2c0 drivers/usb/core/driver.c:293
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+0x1182/0x1ac0 drivers/base/core.c:3622
usb_new_device+0xd80/0x1960 drivers/usb/core/hub.c:2589
hub_port_connect drivers/usb/core/hub.c:5440 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5580 [inline]
port_event drivers/usb/core/hub.c:5740 [inline]
hub_event+0x2daf/0x4e00 drivers/usb/core/hub.c:5822
process_one_work+0xaa2/0x16f0 kernel/workqueue.c:2600
process_scheduled_works kernel/workqueue.c:2667 [inline]
worker_thread+0x896/0x1110 kernel/workqueue.c:2753
kthread+0x33a/0x430 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:304
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Dec 1, 2023, 3:38:11 AM12/1/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages