linux-kernel - Re: [PATCH -next] driver core: fix deadlock in __driver

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: <YqNL6NPgP+cLOy/I@kroah.com>
Date:   Fri, 10 Jun 2022 15:49:28 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Zhang Wensheng <zhangwensheng5@...wei.com>
Cc:     rafael@...nel.org, linux-kernel@...r.kernel.org, yukuai3@...wei.com
Subject: Re: [PATCH -next] driver core: fix deadlock in __driver_attach

On Wed, Jun 08, 2022 at 05:43:55PM +0800, Zhang Wensheng wrote:
> In __driver_attach function, There are also potential AA deadlock
> problem, like the commit b232b02bf3c2 ("driver core: fix deadlock
> in __device_attach").

Potential, but real?

And the codepaths for drivers being added is much different than
devices, please provide the full information like you did in the other
commit.

Also, have you triggered this problem successfully and proven that this
change fixes the issue?

thanks,

greg k-h