From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+13f8286fa2de04a7cd48@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] [usb?] WARNING in asus_remove
Date: Fri, 30 Jan 2026 17:14:12 +0800 [thread overview]
Message-ID: <20260130091428.2426-1-hdanton@sina.com> (raw)
In-Reply-To: <697baa8f.a70a0220.9914.001f.GAE@google.com>
> Date: Thu, 29 Jan 2026 10:44:31 -0800
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 3f24e4edcd1b Add linux-next specific files for 20260128
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12f4b694580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=750532df2c47a03
> dashboard link: https://syzkaller.appspot.com/bug?extid=13f8286fa2de04a7cd48
> compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1188e9b2580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1526fd8a580000
#syz test
--- x/drivers/hid/hid-asus.c
+++ y/drivers/hid/hid-asus.c
@@ -771,6 +771,7 @@ static int asus_kbd_register_leds(struct
if (ret < 0) {
/* No need to have this still around */
devm_kfree(&hdev->dev, drvdata->kbd_backlight);
+ drvdata->kbd_backlight = NULL;
}
return ret;
--
next prev parent reply other threads:[~2026-01-30 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 18:44 syzbot
2026-01-30 6:24 ` Sahil Chandna
2026-01-30 7:04 ` syzbot
2026-02-02 20:28 ` Jiri Kosina
2026-02-02 20:47 ` Jiri Kosina
2026-01-30 7:21 ` [PATCH] test: hid_asus xiaopeitux
2026-01-30 7:41 ` [syzbot] [input?] [usb?] WARNING in asus_remove syzbot
2026-01-30 7:50 ` [PATCH] test: hid_asus xiaopeitux
2026-01-30 8:10 ` [syzbot] [input?] [usb?] WARNING in asus_remove syzbot
2026-01-30 9:14 ` Hillf Danton [this message]
2026-01-30 9:38 ` syzbot
2026-02-03 10:09 ` Sahil Chandna
2026-02-03 13:35 ` 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=20260130091428.2426-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+13f8286fa2de04a7cd48@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®