linux-kernel - Re: [PATCH] driver core: Make probe_type of driver accessible via 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]

Date:   Thu, 8 Jul 2021 20:49:31 +0800
From:   Wenchao Hao <haowenchao@...wei.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     "Rafael J . Wysocki" <rafael@...nel.org>,
        <linux-kernel@...r.kernel.org>, <linfeilong@...wei.com>,
        Wu Bo <wubo40@...wei.com>,
        Zhiqiang Liu <liuzhiqiang26@...wei.com>
Subject: Re: [PATCH] driver core: Make probe_type of driver accessible via
 sysfs

In some scenarios, you need to know whether the probe() callback in struct
driver which triggered by device_add() or driver_register() is called
synchronous or not, and modify this mode according to user requirements.

While kernel now does not open an interface for users to query or
modify, so I add this interface.

I ignored updates to ABI document due to no previous experience with ABI 
change,
and I will bring updates to the ABI in next submission.

On 2021/7/8 20:28, Greg Kroah-Hartman wrote:
> On Thu, Jul 08, 2021 at 08:20:10PM +0800, Wenchao Hao wrote:
>> Like drivers_autoprobe of bus, make probe_type of driver
>> accessible via sysfs, so we can get and set a driver's probe_type
>> happily.
> Why is this needed?  Who will use it?  And where is the
> Documentation/ABI/ file update for this new sysfs file which is required
> for all sysfs files?
>
> thanks,
>
> greg k-h
> .