On Fri, Feb 17, 2017 at 07:36:29PM +0100, Lucas Stach wrote: > On forced unbind the parent lock is taken, as the device might be a USB > device. The device to be unbound might have active consumers, which > must be unbound before calling device_release_driver(), otherwise this > function might deadlock when trying to take the parent lock during > consumer unbind.
Really? What type of device does this fail on today? thanks, greg k-h
