| 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
| ||
|
Message-ID: <d9def9db0711210725x3fe35fedlc67cf637bc9ad27f@mail.gmail.com> Date: Wed, 21 Nov 2007 16:25:08 +0100 From: "Markus Rechberger" <mrechberger@...il.com> To: "Oliver Neukum" <oliver@...kum.org> Cc: "Mark Lord" <lkml@....ca>, linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net, "Laurent Pinchart" <laurentp@...-semaphore.com> Subject: Re: USB deadlock after resume On 11/21/07, Oliver Neukum <oliver@...kum.org> wrote: > Am Mittwoch 21 November 2007 schrieb Markus Rechberger: > > > Which URB is usb_kill_urb() called for? > > > > > > > it's the usb_control_message which calls usb_kill_urb if I haven't got > > it wrong. (if you're looking for some other information please let me > > know) > > Although, I got a bit further with it. The error seems to happen > > earlier already. > > If I load the driver, and do not access the device after suspending > > all usb_control commands fail with -71 eproto. > > A timeout. You should add the RESET_RESUME quirk for your device. > usb_reset_device() from resume() is not a good idea. > ok this is good to know, although I have to stick with kernel 2.6.21.3 here. It's Laurent's driver best would be to check for the specific kernelversion and do whatever is appropriate. thanks, Markus - 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/
Powered by blists - more mailing lists