From: syzbot <syzbot+d627b1495de0e851be32@syzkaller.appspotmail.com>
To: jakovnovak30@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] [usb?] WARNING in smsusb_term_device (2)
Date: Mon, 05 Oct 2026 13:50:03 -0700 [thread overview]
Message-ID: <6ac40d7b.9ad129c8.3858c0.0040.GAE@google.com> (raw)
In-Reply-To: <20261005180430.24652-2-jakovnovak30@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in enable_work
------------[ cut here ]------------
workqueue: work disable count underflowed
WARNING: kernel/workqueue.c:4530 at work_offqd_enable kernel/workqueue.c:4530 [inline], CPU#1: kworker/1:2/5325
WARNING: kernel/workqueue.c:4530 at enable_work+0x1c7/0x230 kernel/workqueue.c:4701, CPU#1: kworker/1:2/5325
Modules linked in:
CPU: 1 UID: 0 PID: 5325 Comm: kworker/1:2 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/2026
Workqueue: usb_hub_wq hub_event
RIP: 0010:work_offqd_enable kernel/workqueue.c:4530 [inline]
RIP: 0010:enable_work+0x1c7/0x230 kernel/workqueue.c:4701
Code: cf 19 38 00 4d 85 f6 75 48 e8 c5 19 38 00 eb 47 e8 be 19 38 00 90 0f 0b 90 e9 bc fe ff ff e8 b0 19 38 00 48 8d 3d 99 1c 26 0e <67> 48 0f b9 3a e9 d2 fe ff ff e8 9a 19 38 00 90 0f 0b 90 e9 1d ff
RSP: 0018:ffffc900048aeae0 EFLAGS: 00010093
RAX: ffffffff818ebc00 RBX: 0000000000000000 RCX: ffff888020bc0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8fb4d8a0
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed10170e7719 R12: 1ffff110053a8807
R13: 0000000001800001 R14: ffff888029d44038 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff888125cc2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd1bfdeb840 CR3: 0000000038686000 CR4: 00000000003526f0
Call Trace:
<TASK>
__cancel_work_sync+0xf8/0x110 kernel/workqueue.c:4571
smsusb_stop_streaming drivers/media/usb/siano/smsusb.c:183 [inline]
smsusb_term_device+0xdd/0x260 drivers/media/usb/siano/smsusb.c:345
smsusb_init_device drivers/media/usb/siano/smsusb.c:499 [inline]
smsusb_probe+0x1aba/0x2280 drivers/media/usb/siano/smsusb.c:577
usb_probe_interface+0x788/0xe50 drivers/usb/core/driver.c:399
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x254/0xae0 drivers/base/dd.c:706
__driver_probe_device+0x1e8/0x360 drivers/base/dd.c:868
driver_probe_device+0x4f/0x240 drivers/base/dd.c:898
__device_attach_driver+0x270/0x410 drivers/base/dd.c:1026
bus_for_each_drv+0x25b/0x2f0 drivers/base/bus.c:500
__device_attach+0x2c7/0x450 drivers/base/dd.c:1098
device_initial_probe+0xa1/0xd0 drivers/base/dd.c:1153
bus_probe_device+0x12d/0x220 drivers/base/bus.c:620
device_add+0x7d7/0xb80 drivers/base/core.c:3776
usb_set_configuration+0x1bb5/0x2260 drivers/usb/core/message.c:2274
usb_generic_driver_probe+0x8d/0x150 drivers/usb/core/generic.c:250
usb_probe_device+0x1c3/0x3b0 drivers/usb/core/driver.c:293
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x254/0xae0 drivers/base/dd.c:706
__driver_probe_device+0x1e8/0x360 drivers/base/dd.c:868
driver_probe_device+0x4f/0x240 drivers/base/dd.c:898
__device_attach_driver+0x270/0x410 drivers/base/dd.c:1026
bus_for_each_drv+0x25b/0x2f0 drivers/base/bus.c:500
__device_attach+0x2c7/0x450 drivers/base/dd.c:1098
device_initial_probe+0xa1/0xd0 drivers/base/dd.c:1153
bus_probe_device+0x12d/0x220 drivers/base/bus.c:620
device_add+0x7d7/0xb80 drivers/base/core.c:3776
usb_new_device+0x99a/0x1680 drivers/usb/core/hub.c:2713
hub_port_connect drivers/usb/core/hub.c:5585 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5725 [inline]
port_event drivers/usb/core/hub.c:5889 [inline]
hub_event+0x28cf/0x4cf0 drivers/usb/core/hub.c:5971
process_one_work kernel/workqueue.c:3396 [inline]
process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
kthread+0x38b/0x470 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
----------------
Code disassembly (best guess):
0: cf iret
1: 19 38 sbb %edi,(%rax)
3: 00 4d 85 add %cl,-0x7b(%rbp)
6: f6 75 48 divb 0x48(%rbp)
9: e8 c5 19 38 00 call 0x3819d3
e: eb 47 jmp 0x57
10: e8 be 19 38 00 call 0x3819d3
15: 90 nop
16: 0f 0b ud2
18: 90 nop
19: e9 bc fe ff ff jmp 0xfffffeda
1e: e8 b0 19 38 00 call 0x3819d3
23: 48 8d 3d 99 1c 26 0e lea 0xe261c99(%rip),%rdi # 0xe261cc3
* 2a: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2f: e9 d2 fe ff ff jmp 0xffffff06
34: e8 9a 19 38 00 call 0x3819d3
39: 90 nop
3a: 0f 0b ud2
3c: 90 nop
3d: e9 .byte 0xe9
3e: 1d .byte 0x1d
3f: ff .byte 0xff
Tested on:
commit: 67f0943b Merge tag 'selinux-pr-20261005' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14f27ec9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=341a98f91c13ec9
dashboard link: https://syzkaller.appspot.com/bug?extid=d627b1495de0e851be32
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1237bec9580000
next parent reply other threads:[~2026-10-05 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261005180430.24652-2-jakovnovak30@gmail.com>
2026-10-05 20:50 ` syzbot [this message]
[not found] <CAFJkwZxNvwciHZP=4MDScjabXro1rPzF08X3_pR+zY7rCN7Pxg@mail.gmail.com>
2026-10-06 9:17 ` syzbot
[not found] <20261005205339.6324-2-jakovnovak30@gmail.com>
2026-10-05 21:43 ` syzbot
[not found] <20261005170717.9242-2-jakovnovak30@gmail.com>
2026-10-05 20:24 ` syzbot
2026-10-05 5:17 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=6ac40d7b.9ad129c8.3858c0.0040.GAE@google.com \
--to=syzbot+d627b1495de0e851be32@syzkaller.appspotmail.com \
--cc=jakovnovak30@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®