linux-kernel - Re: [PATCH v6 5/5] vfio/pci: Implement VFIO_DEVICE_FEATURE_LOW_POWER_ENTRY_WITH

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: <Yv0oH23UYbI/LI+X@nvidia.com>
Date:   Wed, 17 Aug 2022 14:40:47 -0300
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Abhishek Sahu <abhsahu@...dia.com>
Cc:     Alex Williamson <alex.williamson@...hat.com>,
        Cornelia Huck <cohuck@...hat.com>,
        Yishai Hadas <yishaih@...dia.com>,
        Shameer Kolothum <shameerali.kolothum.thodi@...wei.com>,
        Kevin Tian <kevin.tian@...el.com>,
        "Rafael J . Wysocki" <rafael@...nel.org>,
        Max Gurtovoy <mgurtovoy@...dia.com>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
        linux-pm@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH v6 5/5] vfio/pci: Implement
 VFIO_DEVICE_FEATURE_LOW_POWER_ENTRY_WITH_WAKEUP

On Wed, Aug 17, 2022 at 09:34:30PM +0530, Abhishek Sahu wrote:
> On 8/17/2022 7:23 PM, Jason Gunthorpe wrote:
> > On Wed, Aug 17, 2022 at 10:43:23AM +0530, Abhishek Sahu wrote:
> > 
> >> +static int
> >> +vfio_pci_core_pm_entry_with_wakeup(struct vfio_device *device, u32 flags,
> >> +				   void __user *arg, size_t argsz)
> > 
> > This should be
> >   struct vfio_device_low_power_entry_with_wakeup __user *arg
> > 
> 
>  Thanks Jason.
> 
>  I can update this.
> 
>  But if we look the existing code, for example
>  (vfio_ioctl_device_feature_mig_device_state()), then there it still uses
>  'void __user *arg' only. Is this a new guideline which we need to take
>  care ?

I just sent a patch that fixes that too

>  Do we need to keep the IOCTL name alphabetically sorted in the case list.
>  Currently, I have added in the order of IOCTL numbers.

It is generally a good practice to sort lists of things.

Jason