linux-kernel - GHES platform devices

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-next>] [day] [month] [year] [list]

Date:   Wed, 16 Nov 2016 15:36:25 -0600
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Huang Ying <ying.huang@...el.com>
Cc:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: GHES platform devices

Hi Huang,

7ad6e9435596 ("ACPI, APEI, Manage GHES as platform devices") added
platform devices so the GHES driver could be built as a module and
automatically loaded when needed.

Later, 86cd47334b00 ("ACPI, APEI, GHES, Prevent GHES to be built as
module") removed the ability to build GHES as a module.

Should we revert 7ad6e9435596?  It's inconsistent to handle GHES, but
not other error sources, as a platform device.  And having it as a
platform device probably puts gunk in sysfs that we don't need.

Bjorn