From: syzbot <syzbot+25ba18e2c5040447585d@syzkaller.appspotmail.com>
To: stern@rowland.harvard.edu
Cc: greearb@candelatech.com, hdanton@sina.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
michal.pecio@gmail.com, oneukum@suse.com,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] INFO: task hung in usb_bulk_msg (2)
Date: Sun, 08 Feb 2026 07:17:53 -0800 [thread overview]
Message-ID: <6988a921.050a0220.1ad825.0001.GAE@google.com> (raw)
In-Reply-To: <6c618000-fe74-4429-9e91-b8a012598bef@rowland.harvard.edu>
> On Sun, Feb 08, 2026 at 07:03:03AM -0800, syzbot wrote:
>> Hello,
>>
>> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
>> INFO: task hung in usb_bulk_msg
>
> Okay, most likely the reason for the hang is that the count is 0. But
> that doesn't explain everything. Let's get more info.
>
> Alan Stern
>
> #syz test: #https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git da87d45b1951
"#https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git" does not look like a valid git repo address.
>
> ---
> drivers/usb/class/usbtmc.c | 7 +++----
> drivers/usb/gadget/udc/dummy_hcd.c | 11 +++++++++--
> 2 files changed, 12 insertions(+), 6 deletions(-)
>
> Index: usb-devel/drivers/usb/class/usbtmc.c
> ===================================================================
> --- usb-devel.orig/drivers/usb/class/usbtmc.c
> +++ usb-devel/drivers/usb/class/usbtmc.c
> @@ -1362,7 +1362,6 @@ static int send_request_dev_dep_msg_in(s
> data->bTag++;
>
> kfree(buffer);
> - if (retval < 0)
> dev_err(&data->intf->dev, "%s returned %d\n",
> __func__, retval);
>
> @@ -1404,7 +1403,7 @@ static ssize_t usbtmc_read(struct file *
> if (count > INT_MAX)
> count = INT_MAX;
>
> - dev_dbg(dev, "%s(count:%zu)\n", __func__, count);
> + dev_info(dev, "%s(count:%zu)\n", __func__, count);
>
> retval = send_request_dev_dep_msg_in(file_data, count);
>
> @@ -1425,7 +1424,7 @@ static ssize_t usbtmc_read(struct file *
> buffer, bufsize, &actual,
> file_data->timeout);
>
> - dev_dbg(dev, "%s: bulk_msg retval(%u), actual(%d)\n",
> + dev_info(dev, "%s: bulk_msg retval(%u), actual(%d)\n",
> __func__, retval, actual);
>
> /* Store bTag (in case we need to abort) */
> @@ -1470,7 +1469,7 @@ static ssize_t usbtmc_read(struct file *
>
> file_data->bmTransferAttributes = buffer[8];
>
> - dev_dbg(dev, "Bulk-IN header: N_characters(%u), bTransAttr(%u)\n",
> + dev_info(dev, "Bulk-IN header: N_characters(%u), bTransAttr(%u)\n",
> n_characters, buffer[8]);
>
> if (n_characters > remaining) {
> Index: usb-devel/drivers/usb/gadget/udc/dummy_hcd.c
> ===================================================================
> --- usb-devel.orig/drivers/usb/gadget/udc/dummy_hcd.c
> +++ usb-devel/drivers/usb/gadget/udc/dummy_hcd.c
> @@ -762,8 +762,13 @@ static int dummy_dequeue(struct usb_ep *
> ep = usb_ep_to_dummy_ep(_ep);
> dum = ep_to_dummy(ep);
>
> - if (!dum->driver)
> + if (!dum->driver) {
> + dev_info(udc_dev(dum), "Got dequeue, no driver\n");
> return -ESHUTDOWN;
> + }
> + dev_info(udc_dev(dum),
> + "dequeuing req %p from %s, len %d buf %p\n",
> + req, _ep->name, _req->length, _req->buf);
>
> spin_lock_irqsave(&dum->lock, flags);
> list_for_each_entry(iter, &ep->queue, queue) {
> @@ -777,12 +782,14 @@ static int dummy_dequeue(struct usb_ep *
> }
>
> if (retval == 0) {
> - dev_dbg(udc_dev(dum),
> + dev_info(udc_dev(dum),
> "dequeued req %p from %s, len %d buf %p\n",
> req, _ep->name, _req->length, _req->buf);
> spin_unlock(&dum->lock);
> usb_gadget_giveback_request(_ep, _req);
> spin_lock(&dum->lock);
> + } else {
> + dev_info(udc_dev(dum), "request not found\n");
> }
> spin_unlock_irqrestore(&dum->lock, flags);
> return retval;
next prev parent reply other threads:[~2026-02-08 15:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 6:34 [syzbot] [usb?] INFO: task hung in usb_bulk_msg (2) syzbot
2026-02-08 8:55 ` Hillf Danton
2026-02-08 14:47 ` Alan Stern
2026-02-08 15:03 ` syzbot
2026-02-08 15:17 ` Alan Stern
2026-02-08 15:17 ` syzbot [this message]
2026-02-08 15:19 ` Alan Stern
2026-02-08 15:50 ` syzbot
2026-02-08 20:10 ` Alan Stern
2026-02-08 20:10 ` syzbot
2026-02-08 20:13 ` Alan Stern
2026-02-08 20:34 ` syzbot
2026-02-08 21:32 ` Alan Stern
2026-02-08 21:53 ` syzbot
2026-02-09 1:26 ` Alan Stern
2026-02-09 1:46 ` syzbot
2026-02-09 16:34 ` Alan Stern
2026-02-09 17:30 ` syzbot
2026-02-13 21:30 ` Alan Stern
2026-02-13 21:49 ` syzbot
2026-02-09 10:03 ` Oliver Neukum
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=6988a921.050a0220.1ad825.0001.GAE@google.com \
--to=syzbot+25ba18e2c5040447585d@syzkaller.appspotmail.com \
--cc=greearb@candelatech.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
--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