All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: syzbot <syzbot+fd7be5ad9795b7f29df3@syzkaller.appspotmail.com>,
	dakr@kernel.org, driver-core@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] INFO: task hung in unbind_store
Date: Thu, 27 Aug 2026 11:08:03 +0200	[thread overview]
Message-ID: <20260827110803.49790ae3.michal.pecio@gmail.com> (raw)
In-Reply-To: <20260827110006.66b07ea4.michal.pecio@gmail.com>

On Thu, 27 Aug 2026 11:00:06 +0200, Michal Pecio wrote:
> And something is also wrong with those timeouts, because 20 times 5s
> should still be less than 143 s. I asked Syzbot to try 500ms instead,
> which ended up being over 3s in practice:
> 
> [  566.662036][ T6636] usb 4-1: sisusb_send_bulk_msg()
> [  569.717341][ T6636] usb 4-1: sisusb_send_bulk_msg()
> [  572.777761][ T6636] usb 4-1: sisusb_send_bulk_msg()
> [  575.845365][ T6636] usb 4-1: sisusb_send_bulk_msg()
> 
> Same on my system, but patch below reduces the timeout to 500ms.
> 
> I have no idea what's happening here. Looks like a bug?
> Is it known that jiffies are totally unreliable like that?

Sorry for the noise, timeouts are 500ms as inteneded but the function
tries 6 times, which makes it 3 seconds.

  reply	other threads:[~2026-08-27  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 11:40 [syzbot] [usb?] INFO: task hung in unbind_store 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 [this message]
2026-08-26 14:51 ` syzbot
2026-08-27  6:02   ` Michal Pecio
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=20260827110803.49790ae3.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.