linux-kernel - Re: [linux-usb-devel] [PATCH 2/2] usbatm: Detect usb device shutdown and ignore failed urbs.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 23 Feb 2007 11:16:24 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Duncan Sands <duncan.sands@...h.u-psud.fr>
cc:	Pete Zaitcev <zaitcev@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	<linux-usb-devel@...ts.sourceforge.net>,
	Simon Arlott <254ad70138dc1cdf241hjzcr0007jhhw@...nder.lp0.eu>
Subject: Re: [linux-usb-devel] [PATCH 2/2] usbatm: Detect usb device shutdown
 and ignore failed urbs.

On Fri, 23 Feb 2007, Duncan Sands wrote:

> if you get ESHUTDOWN, does that mean that you are about to be disconnected,
> i.e. the disconnect method is about to be called?  Or is it possible for the
> device to just sit there disabled, but not disconnected?

It is possible to receive ESHUTDOWN without being disconnected.  For 
instance, a race with suspend could cause it to happen (although if your 
driver is written correctly that race should never occur).  Another more 
likely scenario is that you have an active URB while calling 
usb_set_interface(); the endpoints for the old altsetting get disabled and 
the URB returns with an ESHUTDOWN error.

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/