linux-kernel - Re: USB deadlock after resume

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]

Message-Id: <200711211603.20173.oliver@neukum.org>
Date:	Wed, 21 Nov 2007 16:03:19 +0100
From:	Oliver Neukum <oliver@...kum.org>
To:	Felipe Balbi <me@...ipebalbi.com>
Cc:	Markus Rechberger <mrechberger@...il.com>, 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

Am Mittwoch 21 November 2007 schrieb Felipe Balbi:
> Hi,
> 
> On Wed, 21 Nov 2007 15:37:20 +0100, "Markus Rechberger"
> <mrechberger@...il.com> wrote:

> > 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.
> 
> This device shouldn't be suspended. AFAIK it should have auto_suspend
> disabled
> by default.
> 
> Try adding this device to drivers/usb/core/quirks.c with
> USB_QUIRK_NO_AUTOSUSPEND flag set. Something like:

Unless the device sets a flag it won't be autosuspended. Nevertheless
it will and must be suspended as the whole system is supended.

	Regards
		Oliver
-
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/