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: <9f0becda-4ee1-1330-91c4-df919507cb2c@ti.com>
Date:   Tue, 21 May 2019 14:15:01 -0500
From:   Kishon Vijay Abraham I <kishon@...com>
To:     Alan Cooper <alcooperx@...il.com>,
        ": Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: Generic PHY "unload" crash

Hi Alan,

On 21/05/19 1:40 PM, Alan Cooper wrote:
> I'm seeing an issue on a system where I have a generic PHY that is
> used by a USB XHCI driver. The XHCI driver does the phy_init() in
> probe and the phy_exit() in remove. The problem happens when I use
> sysfs to "unload" the PHY driver before doing an unload of the XHCI
> driver. This is a result of the XHCI driver calling into the PHY
> driver's phy_exit routine after it's been removed. It seems like this
> issue will exist for other PHY provider/user pairs and I don't see an
> easy solution. I was wondering if anyone had any suggestions on how to
> solve this problem.

Can you share the crash dump please?

Thanks
Kishon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ