linux-kernel - Re: [RFC PATCH v3] driver core: hold dev's parent lock when needed

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:   Tue, 29 May 2018 18:59:00 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Martin Liu <liumartin@...gle.com>
Cc:     heikki.krogerus@...ux.intel.com, johan@...nel.org,
        stern@...land.harvard.edu, andy.shevchenko@...il.com,
        linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
        jenhaochen@...gle.com
Subject: Re: [RFC PATCH v3] driver core: hold dev's parent lock when needed

On Wed, May 30, 2018 at 12:34:29AM +0800, Martin Liu wrote:
> SOC have internal I/O buses that can't be proved for devices. The
> devices on the buses can be accessed directly without additinal
> configuration required. This type of bus is represented as
> "simple-bus". In some platforms, we name "soc" with "simple-bus"
> attribute and many devices are hooked under it desribed in DT
> (device tree).

<snip>

Hint, I don't apply "RFC" patches as obviously the author does not think
it is good enough to be merged :)