From: syzbot <syzbot+13f8286fa2de04a7cd48@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xiaopei01@kylinos.cn, xiaopeitux@foxmail.com
Subject: Re: [syzbot] [input?] [usb?] WARNING in asus_remove
Date: Fri, 30 Jan 2026 00:10:01 -0800 [thread overview]
Message-ID: <697c6759.a00a0220.35f26.0012.GAE@google.com> (raw)
In-Reply-To: <tencent_C0A49257DF09D0DC82EB5F840A370F553C06@qq.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in asus_remove
usb 1-1: USB disconnect, device number 2
------------[ cut here ]------------
!work->func
WARNING: kernel/workqueue.c:4292 at __flush_work+0xb43/0xc50 kernel/workqueue.c:4292, CPU#1: kworker/1:4/5981
Modules linked in:
CPU: 1 UID: 0 PID: 5981 Comm: kworker/1:4 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Workqueue: usb_hub_wq hub_event
RIP: 0010:__flush_work+0xb43/0xc50 kernel/workqueue.c:4292
Code: 75 54 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 cc 87 37 00 90 0f 0b 90 e9 7c ff ff ff e8 be 87 37 00 90 <0f> 0b 90 31 c0 48 bb f8 f8 f8 f8 f8 f8 f8 f8 e9 64 ff ff ff e8 a4
RSP: 0018:ffffc90003a9f080 EFLAGS: 00010293
RAX: ffffffff818db1c2 RBX: 1ffff1100e8eab1c RCX: ffff88802742dac0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8880747558c8
RBP: ffffc90003a9f238 R08: ffffffff903284b7 R09: 1ffffffff2065096
R10: dffffc0000000000 R11: fffffbfff2065097 R12: dffffc0000000000
R13: ffff8880747558e0 R14: 1ffff92000753e18 R15: ffff8880747558c8
FS: 0000000000000000(0000) GS:ffff888125152000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f64d7e51e9c CR3: 000000006163c000 CR4: 00000000003526f0
Call Trace:
<TASK>
__cancel_work_sync+0xbe/0x110 kernel/workqueue.c:4451
asus_remove+0x143/0x180 drivers/hid/hid-asus.c:1355
hid_device_remove+0x228/0x370 drivers/hid/hid-core.c:-1
device_remove drivers/base/dd.c:571 [inline]
__device_release_driver drivers/base/dd.c:1284 [inline]
device_release_driver_internal+0x46f/0x860 drivers/base/dd.c:1307
bus_remove_device+0x34d/0x440 drivers/base/bus.c:616
device_del+0x527/0x8f0 drivers/base/core.c:3878
hid_remove_device drivers/hid/hid-core.c:3008 [inline]
hid_destroy_device+0x6b/0x1b0 drivers/hid/hid-core.c:3030
usbhid_disconnect+0x9f/0xc0 drivers/hid/usbhid/hid-core.c:1477
usb_unbind_interface+0x26e/0x910 drivers/usb/core/driver.c:458
device_remove drivers/base/dd.c:573 [inline]
__device_release_driver drivers/base/dd.c:1284 [inline]
device_release_driver_internal+0x4d9/0x860 drivers/base/dd.c:1307
bus_remove_device+0x34d/0x440 drivers/base/bus.c:616
device_del+0x527/0x8f0 drivers/base/core.c:3878
usb_disable_device+0x3d4/0x8d0 drivers/usb/core/message.c:1418
usb_disconnect+0x32f/0x990 drivers/usb/core/hub.c:2345
hub_port_connect drivers/usb/core/hub.c:5407 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
port_event drivers/usb/core/hub.c:5871 [inline]
hub_event+0x1cc9/0x4f30 drivers/usb/core/hub.c:5953
process_one_work+0x949/0x15a0 kernel/workqueue.c:3279
process_scheduled_works kernel/workqueue.c:3362 [inline]
worker_thread+0xb46/0x1140 kernel/workqueue.c:3443
kthread+0x388/0x470 kernel/kthread.c:467
ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
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=11e1a5b2580000
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=17fc1644580000
next prev parent reply other threads:[~2026-01-30 8:10 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
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 [this message]
2026-01-30 9:14 ` [syzbot] [input?] [usb?] WARNING in asus_remove 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=697c6759.a00a0220.35f26.0012.GAE@google.com \
--to=syzbot+13f8286fa2de04a7cd48@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiaopei01@kylinos.cn \
--cc=xiaopeitux@foxmail.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