From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+f8fb5598924c7e645553@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] [usb?] WARNING: ODEBUG bug in hid_device_remove
Date: Mon, 17 Aug 2026 07:51:45 +0800 [thread overview]
Message-ID: <20260816235146.1223-1-hdanton@sina.com> (raw)
In-Reply-To: <6a802643.9ebadd4d.20b15e.000b.GAE@google.com>
> Date: Sat, 15 Aug 2026 01:41:39 -0700 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 28d012efb432 Add linux-next specific files for 20260812
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1613f479580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=5a13c7bc480b5c3f
> dashboard link: https://syzkaller.appspot.com/bug?extid=f8fb5598924c7e645553
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17bc1c79580000
#syz test
--- x/drivers/hid/hid-corsair.c
+++ y/drivers/hid/hid-corsair.c
@@ -524,6 +524,7 @@ static void k90_cleanup_backlight(struct
if (drvdata->backlight) {
drvdata->backlight->removed = true;
+ disable_work(&drvdata->backlight->work);
cancel_work_sync(&drvdata->backlight->work);
led_classdev_unregister(&drvdata->backlight->cdev);
kfree(drvdata->backlight->cdev.name);
@@ -540,6 +541,7 @@ static void k90_cleanup_macro_functions(
sysfs_remove_group(&dev->dev.kobj, &k90_attr_group);
k90->record_led.removed = true;
+ disable_work(&k90->record_led.work);
cancel_work_sync(&k90->record_led.work);
led_classdev_unregister(&k90->record_led.cdev);
kfree(k90->record_led.cdev.name);
--
next prev parent reply other threads:[~2026-08-16 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 8:41 [syzbot] [input?] [usb?] WARNING: ODEBUG bug in hid_device_remove syzbot
2026-08-16 2:52 ` Hillf Danton
2026-08-16 3:53 ` syzbot
2026-08-16 23:51 ` Hillf Danton [this message]
2026-08-17 2:15 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260816235146.1223-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+f8fb5598924c7e645553@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.