linux-kernel - Re: [PATCH v2] Add driver to force WMI Thunderbolt controller power status

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: <20170911094614.GO2477@lahna.fi.intel.com>
Date:   Mon, 11 Sep 2017 12:46:14 +0300
From:   Mika Westerberg <mika.westerberg@...ux.intel.com>
To:     Darren Hart <dvhart@...radead.org>
Cc:     Mario.Limonciello@...l.com, linux-kernel@...r.kernel.org,
        platform-driver-x86@...r.kernel.org, hughsient@...il.com,
        yehezkelshb@...il.com
Subject: Re: [PATCH v2] Add driver to force WMI Thunderbolt controller power
 status

On Mon, Sep 11, 2017 at 02:39:55AM -0700, Darren Hart wrote:
> Which device are you referring to? This attribute is bound to the device
> identified by the WMI GUID, and should be independent from the controller or any
> thunderbolt connected physical device.

I refer to "wdev->dev" whatever that is. That device has been created
long time before this driver is probed and thus userspace already got
the KOBJ_ADD uevent.