From: Michal Pecio <michal.pecio@gmail.com>
To: syzbot <syzbot+fd7be5ad9795b7f29df3@syzkaller.appspotmail.com>
Cc: dakr@kernel.org, driver-core@lists.linux.dev,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, rafael@kernel.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] INFO: task hung in unbind_store
Date: Thu, 27 Aug 2026 08:02:26 +0200 [thread overview]
Message-ID: <20260827080226.4ec229d3.michal.pecio@gmail.com> (raw)
In-Reply-To: <6a8efd77.50659fcc.60cd.0001.GAE@google.com>
On Wed, 26 Aug 2026 07:51:35 -0700, syzbot wrote:
> INFO: task syz.0.23:5988 blocked for more than 143 seconds.
> Not tainted syzkaller #0
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> task:syz.0.23 state:D stack:27344 pid:5988 tgid:5988 ppid:5772 task_flags:0x400140 flags:0x08080002
> Call Trace:
> <TASK>
> context_switch kernel/sched/core.c:5520 [inline]
> __schedule+0x17d4/0x5820 kernel/sched/core.c:7270
> __schedule_loop kernel/sched/core.c:7347 [inline]
> schedule+0x164/0x2b0 kernel/sched/core.c:7362
> schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7419
> __mutex_lock_common kernel/locking/mutex.c:726 [inline]
> __mutex_lock+0x7c1/0x1550 kernel/locking/mutex.c:821
> device_lock include/linux/device.h:1104 [inline]
> __device_driver_lock drivers/base/dd.c:1170 [inline]
> device_release_driver_internal+0x93/0x880 drivers/base/dd.c:1369
> unbind_store+0x1a1/0x1d0 drivers/base/bus.c:244
#syz test
--- a/drivers/usb/misc/sisusbvga/sisusbvga.c
+++ b/drivers/usb/misc/sisusbvga/sisusbvga.c
@@ -323,6 +323,7 @@ static int sisusb_send_bulk_msg(struct sisusb_usb_data *sisusb, int ep, int len,
unsigned int pipe;
char *buffer;
+ dev_info(&sisusb->sisusb_dev->dev, "sisusb_send_bulk_msg()\n");
(*bytes_written) = 0;
/* Sanity check */
@@ -378,7 +379,7 @@ static int sisusb_send_bulk_msg(struct sisusb_usb_data *sisusb, int ep, int len,
result = sisusb_bulkout_msg(sisusb, index, pipe,
buffer, thispass, &transferred_len,
- async ? 0 : 5 * HZ, tflags);
+ async ? 0 : HZ / 2, tflags);
if (result == -ETIMEDOUT) {
next prev parent reply other threads:[~2026-08-27 6:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 11:40 syzbot
2026-08-23 11:46 ` Greg KH
2026-08-23 14:40 ` Alan Stern
2026-08-23 17:28 ` Greg KH
2026-08-24 0:29 ` Alan Stern
2026-08-27 9:00 ` Michal Pecio
2026-08-27 9:08 ` Michal Pecio
2026-08-26 14:51 ` syzbot
2026-08-27 6:02 ` Michal Pecio [this message]
2026-08-27 7:44 ` 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=20260827080226.4ec229d3.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+fd7be5ad9795b7f29df3@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®