From: syzbot <syzbot+13f8286fa2de04a7cd48@syzkaller.appspotmail.com>
To: bentiss@kernel.org, chandna.sahil@gmail.com, jikos@kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] [usb?] WARNING in asus_remove
Date: Thu, 29 Jan 2026 23:04:05 -0800 [thread overview]
Message-ID: <697c57e5.a00a0220.35f26.0011.GAE@google.com> (raw)
In-Reply-To: <aXxOhV79TnuYaw0-@chandna.localdomain>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+13f8286fa2de04a7cd48@syzkaller.appspotmail.com
Tested-by: syzbot+13f8286fa2de04a7cd48@syzkaller.appspotmail.com
Tested on:
commit: 33a647c6 Add linux-next specific files for 20260129
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=140cf6ef980000
kernel config: https://syzkaller.appspot.com/x/.config?x=aef5831c38e37e48
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
patch: https://syzkaller.appspot.com/x/patch.diff?x=13ec1644580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-01-30 7:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 18:44 [syzbot] [input?] [usb?] WARNING in asus_remove syzbot
2026-01-30 6:24 ` Sahil Chandna
2026-01-30 7:04 ` syzbot [this message]
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
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=697c57e5.a00a0220.35f26.0011.GAE@google.com \
--to=syzbot+13f8286fa2de04a7cd48@syzkaller.appspotmail.com \
--cc=bentiss@kernel.org \
--cc=chandna.sahil@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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