Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933125AbXBWQQ2 (ORCPT ); Fri, 23 Feb 2007 11:16:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933127AbXBWQQ1 (ORCPT ); Fri, 23 Feb 2007 11:16:27 -0500 Received: from firewall.rowland.harvard.edu ([140.247.233.35]:27913 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with SMTP id S933125AbXBWQQ1 (ORCPT ); Fri, 23 Feb 2007 11:16:27 -0500 Date: Fri, 23 Feb 2007 11:16:24 -0500 (EST) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: Duncan Sands cc: Pete Zaitcev , Linux Kernel Mailing List , , Simon Arlott <254ad70138dc1cdf241hjzcr0007jhhw@thunder.lp0.eu> Subject: Re: [linux-usb-devel] [PATCH 2/2] usbatm: Detect usb device shutdown and ignore failed urbs. In-Reply-To: <200702231036.14048.duncan.sands@math.u-psud.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 913 Lines: 20 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/