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
| ||
|
Message-ID: <20170914145919.GU2477@lahna.fi.intel.com> Date: Thu, 14 Sep 2017 17:59:19 +0300 From: Mika Westerberg <mika.westerberg@...ux.intel.com> To: Mario.Limonciello@...l.com Cc: lukas@...ner.de, dvhart@...radead.org, linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org, hughsient@...il.com, yehezkelshb@...il.com Subject: Re: [PATCH v3] Add driver to force WMI Thunderbolt controller power status On Thu, Sep 14, 2017 at 02:52:27PM +0000, Mario.Limonciello@...l.com wrote: > > Looking at drivers/platform/x86/wmi.c:wmi_dev_uevent() it seems that > > a modalias consisting of "wmi:" followed by the GUID is sent to udevd. > > For udevd to then load the module, I suspect you need to add a > > MODULE_DEVICE_TABLE(wmi, ...) to your driver. > > Ah, you're looking for this code from the WMI bus driver: > https://github.com/torvalds/linux/blob/master/drivers/platform/x86/wmi.c#L724 > > That happens when the bus is initialized. That's right you get the uevent and whatnot but Lucas means that if you don't have MODULE_DEVICE_TABLE(wmi, ...) in the driver, udev cannot load the module automatically when the device appears.
Powered by blists - more mailing lists