Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1742449

Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

From Darren Hart <dvhart@infradead.org>
Newsgroups linux.kernel
Subject Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers
Date 2017-09-30 04:00 +0200
Message-ID <uvfeq-5PS-15@gated-at.bofh.it> (permalink)
References <uuyj7-40H-7@gated-at.bofh.it> <uuyj7-40H-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Sep 27, 2017 at 11:02:16PM -0500, Mario Limonciello wrote:
> For WMI operations that are only Set or Query read or write sysfs
> attributes created by WMI vendor drivers make sense.
> 
> For other WMI operations that are run on Method, there needs to be a
> way to guarantee to userspace that the results from the method call
> belong to the data request to the method call.  Sysfs attributes don't
> work well in this scenario because two userspace processes may be
> competing at reading/writing an attribute and step on each other's
> data.
> 
> When a WMI vendor driver declares a set of functions in a
> file_operations object the WMI bus driver will create a character
> device that maps to those file operations.
> 
> That character device will correspond to this path:
> /dev/wmi/$driver
> 
> This policy is selected as one driver may map and use multiple
> GUIDs and it would be better to only expose a single character
> device.
> 
> The WMI vendor drivers will be responsible for managing access to
> this character device and proper locking on it.
> 
> When a WMI vendor driver is unloaded the WMI bus driver will clean
> up the character device.
> 
> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
> ---
>  drivers/platform/x86/wmi.c | 98 +++++++++++++++++++++++++++++++++++++++++++---
>  include/linux/wmi.h        |  1 +
>  2 files changed, 94 insertions(+), 5 deletions(-)

+Greg, Rafael, Matthew, and Christoph

You each provided feedback regarding the method of exposing WMI methods
to userspace. This and subsequent patches from Mario lay some of the
core groundwork.

They implement an implicit whitelist as only drivers requesting the char
dev will see it created.

https://lkml.org/lkml/2017/9/28/8

-- 
Darren Hart
VMware Open Source Technology Center

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers Mario Limonciello <mario.limonciello@dell.com> - 2017-09-28 06:10 +0200
  Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when  requested by drivers Darren Hart <dvhart@infradead.org> - 2017-09-30 04:00 +0200
    Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when  requested by drivers Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-30 10:20 +0200
      RE: [PATCH v3 4/8] platform/x86: wmi: create character devices when  requested by drivers <Mario.Limonciello@dell.com> - 2017-09-30 21:30 +0200
        Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when  requested by drivers Greg KH <gregkh@linuxfoundation.org> - 2017-10-01 15:30 +0200
          RE: [PATCH v3 4/8] platform/x86: wmi: create character devices when  requested by drivers <Mario.Limonciello@dell.com> - 2017-10-01 16:30 +0200
            Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when  requested by drivers Greg KH <gregkh@linuxfoundation.org> - 2017-10-01 20:10 +0200
      Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when  requested by drivers Darren Hart <dvhart@infradead.org> - 2017-10-02 03:00 +0200
        Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when  requested by drivers Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-10-02 11:30 +0200

csiph-web