linux-kernel - Re: [PATCH] driver core: Add deferred_probe attribute to devices in sysfs

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: <20160831131048.GA32056@kroah.com>
Date:   Wed, 31 Aug 2016 15:10:48 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Ben Hutchings <ben.hutchings@...ethink.co.uk>
Cc:     linux-kernel@...r.kernel.org,
        CT kernel <linux-kernel@...ts.codethink.co.uk>
Subject: Re: [PATCH] driver core: Add deferred_probe attribute to devices in
 sysfs

On Tue, Aug 16, 2016 at 02:34:18PM +0100, Ben Hutchings wrote:
> It is sometimes useful to know that a device is on the deferred probe
> list rather than, say, not having a driver available.  Expose this
> information to user-space.

What can someone use this for?  It's an attribute that for 99.9% of the
time will always be the same value.

I can see when debugging it might be nice, but what can a user do with
this?

thanks,

greg k-h