From: Alan Stern <stern@rowland.harvard.edu>
To: Oliver Neukum <oneukum@suse.com>
Cc: Johan Hovold <johan@kernel.org>, Greg KH <greg@kroah.com>,
syzbot <syzbot+ada0f7d3d9fd2016d927@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com,
USB mailing list <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] USB: core: Make usb_start_wait_urb() interruptible
Date: Mon, 30 Aug 2021 12:09:14 -0400 [thread overview]
Message-ID: <20210830160914.GC332514@rowland.harvard.edu> (raw)
In-Reply-To: <0e3214c8-a82f-d117-962e-326817244c9a@suse.com>
On Mon, Aug 30, 2021 at 05:11:53PM +0200, Oliver Neukum wrote:
>
> On 30.08.21 16:46, Alan Stern wrote:
> > Do you have alternative suggestions? I don't think we want special
> > interruptible versions of usb_control_msg() and usb_bulk_msg() just for
> > use by usbfs.
>
> Hi,
>
> why not just pass a flag?
We could. But you're ignoring the question I asked earlier in that
email: Is a 5-second uninterruptible delay (the default USB control
timeout) acceptable in general?
Alan Stern
next prev parent reply other threads:[~2021-08-30 16:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 15:52 [syzbot] INFO: task hung in do_proc_bulk syzbot
2021-08-28 18:03 ` Alan Stern
2021-08-28 20:05 ` syzbot
2021-08-29 1:58 ` [PATCH] USB: core: Make usb_start_wait_urb() interruptible Alan Stern
2021-08-30 7:56 ` Johan Hovold
2021-08-30 14:46 ` Alan Stern
2021-08-30 15:11 ` Oliver Neukum
2021-08-30 16:09 ` Alan Stern [this message]
2021-08-31 8:52 ` Oliver Neukum
2021-08-31 9:13 ` Johan Hovold
2021-08-31 10:47 ` Oliver Neukum
2021-08-31 11:02 ` Oliver Neukum
2021-08-31 11:10 ` Johan Hovold
2021-08-31 17:03 ` Alan Stern
2021-09-01 8:16 ` Oliver Neukum
2021-09-02 20:04 ` [syzbot] INFO: task hung in do_proc_bulk Alan Stern
2021-09-02 20:46 ` 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=20210830160914.GC332514@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=greg@kroah.com \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=syzbot+ada0f7d3d9fd2016d927@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;
as well as URLs for NNTP newsgroup(s).