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  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]
Date:   Thu, 2 Nov 2017 11:32:36 +0200
From:   Adrian Hunter <>
To:     Greg Kroah-Hartman <>
Cc:     "Rafael J. Wysocki" <>,
        linux-kernel <>
Subject: Re: [PATCH] driver core: Fix device link deferred probe

On 02/11/17 11:33, Greg Kroah-Hartman wrote:
> On Thu, Nov 02, 2017 at 11:22:53AM +0200, Adrian Hunter wrote:
>> A device probe deferred because of a device link is never probed again
>> because it is not added to the deferred_probe_pending_list. Add it, taking
>> care of the race with driver_deferred_probe_trigger().
> What hardware is triggering this?  Is this a new thing, or something
> that has always happened?

I just found it trying to use device links in new code.  As far as I know it
is not a problem that anyone else is experiencing yet.

Powered by blists - more mailing lists