From: syzbot <syzbot+d627b1495de0e851be32@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, neganhat@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] [usb?] WARNING in smsusb_term_device (2)
Date: Tue, 06 Oct 2026 02:17:02 -0700 [thread overview]
Message-ID: <6ac4bc8e.fe639fcc.32b100.0000.GAE@google.com> (raw)
In-Reply-To: <CAFJkwZxNvwciHZP=4MDScjabXro1rPzF08X3_pR+zY7rCN7Pxg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in usb_free_urb
smsmdtv:smscore_set_device_mode: return error code -71.
smsmdtv:smscore_start_device: set device mode failed , rc -71
smsusb:smsusb_init_device: smscore_start_device(...) failed
------------[ cut here ]------------
!PageLargeKmalloc(page)
WARNING: mm/slub.c:6734 at free_large_kmalloc+0x97/0x110 mm/slub.c:6734, CPU#1: kworker/1:3/5087
Modules linked in:
CPU: 1 UID: 0 PID: 5087 Comm: kworker/1:3 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:free_large_kmalloc+0x97/0x110 mm/slub.c:6734
Code: 8b 43 30 83 f8 ff 74 13 25 00 00 00 ff 3d 00 00 00 f8 75 7a c7 43 30 ff ff ff ff 48 89 df 89 ee 5b 41 5e 5d e9 6a 99 fc ff 90 <0f> 0b 90 48 89 df 48 c7 c6 a7 90 88 8d 5b 41 5e 5d e9 73 3c 00 ff
RSP: 0018:ffffc90004326af8 EFLAGS: 00010206
RAX: 00000000ff000000 RBX: ffffea0001658c40 RCX: 0000000000000001
RDX: 0000000000000000 RSI: ffff888059631000 RDI: ffffea0001658c40
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed10055d3561 R12: ffff88803ae5f000
R13: ffff88803ae5f428 R14: ffff88802ae9ab60 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff888125cc2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f55c6bef255 CR3: 00000000469dc000 CR4: 00000000003526f0
Call Trace:
<TASK>
urb_destroy drivers/usb/core/urb.c:25 [inline]
kref_put include/linux/kref.h:65 [inline]
usb_free_urb+0xd0/0x120 drivers/usb/core/urb.c:96
smsusb_term_device+0x1e9/0x410 drivers/media/usb/siano/smsusb.c:352
smsusb_init_device drivers/media/usb/siano/smsusb.c:497 [inline]
smsusb_probe+0x1aba/0x2280 drivers/media/usb/siano/smsusb.c:575
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>
Tested on:
commit: 6addb4f3 Merge tag 'edac_urgent_for_v7.3_rc6' of git:/..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=152a01c9580000
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=150b1ff5580000
next parent reply other threads:[~2026-10-06 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFJkwZxNvwciHZP=4MDScjabXro1rPzF08X3_pR+zY7rCN7Pxg@mail.gmail.com>
2026-10-06 9:17 ` syzbot [this message]
[not found] <20261006105153.8625-2-jakovnovak30@gmail.com>
2026-10-06 17:16 ` syzbot
[not found] <20261006103451.5210-2-jakovnovak30@gmail.com>
2026-10-06 15:40 ` syzbot
[not found] <20261005205339.6324-2-jakovnovak30@gmail.com>
2026-10-05 21:43 ` syzbot
[not found] <20261005180430.24652-2-jakovnovak30@gmail.com>
2026-10-05 20:50 ` 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=6ac4bc8e.fe639fcc.32b100.0000.GAE@google.com \
--to=syzbot+d627b1495de0e851be32@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neganhat@gmail.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®