linux-kernel - Re: [PATCH] driver core: unbind consumers before locking parent on device unbind

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: <20170217184242.GA11935@kroah.com>
Date:   Fri, 17 Feb 2017 10:42:42 -0800
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Lucas Stach <l.stach@...gutronix.de>
Cc:     linux-kernel@...r.kernel.org, patchwork-lst@...gutronix.de,
        kernel@...gutronix.de
Subject: Re: [PATCH] driver core: unbind consumers before locking parent on
 device unbind

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