linux-kernel - Re: [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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 23 Feb 2007 10:36:13 +0100
From:	Duncan Sands <duncan.sands@...h.u-psud.fr>
To:	Pete Zaitcev <zaitcev@...hat.com>
Cc:	Simon Arlott <254ad70138dc1cdf241hjzcr0007jhhw@...nder.lp0.eu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-usb-devel@...ts.sourceforge.net
Subject: Re: [PATCH 2/2] usbatm: Detect usb device shutdown and ignore failed urbs.

Hi Pete,

On Friday 23 February 2007 00:53:18 Pete Zaitcev wrote:
> On Thu, 22 Feb 2007 11:43:38 +0100, Duncan Sands <duncan.sands@...h.u-psud.fr> wrote:
> > > +		/* the module/device has probably been removed */
> > > +		if (urb->status == -ESHUTDOWN)
> > > +			return;
> > > +
> > >  		if (printk_ratelimit())
> > >  			atm_warn(channel->usbatm, "%s: urb 0x%p failed (%d)!\n",
> > >  				__func__, urb, urb->status);
> > 
> > I would rather just suppress the warning in this case, and still do the delayed
> > schedule of the tasklet, in case this error was spurious and we're not really
> > about to be disconnected.
> 
> I disagree. If ESHUTDOWN is received, the endpoint is definitely gone.
> I can see why you might want to retry EPROTO, ELISEQ, etc. but this
> case is different.

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?

Thanks,

Duncan.
-
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/