linux-kernel - Re: [EXT] Re: [PATCH] Uwb: Nxp: sr1xx: Uwb driver support for sr1xx series chip

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: <YjCHNlC2Xc1QoTzQ@kroah.com>
Date:   Tue, 15 Mar 2022 13:31:50 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Manjunatha Venkatesh <manjunatha.venkatesh@....com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "will@...nel.org" <will@...nel.org>,
        "axboe@...nel.dk" <axboe@...nel.dk>,
        "mb@...htnvm.io" <mb@...htnvm.io>,
        "ckeepax@...nsource.cirrus.com" <ckeepax@...nsource.cirrus.com>,
        "arnd@...db.d" <arnd@...db.d>, "mst@...hat.com" <mst@...hat.com>,
        "javier@...igon.com" <javier@...igon.com>,
        "mikelley@...rosoft.com" <mikelley@...rosoft.com>,
        "jasowang@...hat.com" <jasowang@...hat.com>,
        "sunilmut@...rosoft.com" <sunilmut@...rosoft.com>,
        "bjorn.andersson@...aro.org" <bjorn.andersson@...aro.org>,
        "rvmanjumce@...il.com" <rvmanjumce@...il.com>
Subject: Re: [EXT] Re: [PATCH] Uwb: Nxp: sr1xx: Uwb driver support for sr1xx
 series chip

On Tue, Mar 15, 2022 at 10:43:47AM +0000, Manjunatha Venkatesh wrote:
> >> +     sr1xx_dev = filp->private_data;
> >> +     switch (cmd) {
> >> +     case SR1XX_SET_PWR:
> > You have custom ioctls on a device node, that's not very "subsystem"
> > like at all.
> >
> > You need to define a standard user/kernel api for this subsystem, do not
> > make it "whatever the device wants" like this currently is.
> >
> > And where is the userspace code that talks this brand new api?  We need
> > to see that so we can properly determine if this is all working
> > properly.
> Currently these ioctl calls used for handling proprietary operation with 
> respect to SR1xx chip.
> corresponding user space UWB code is proprietary and might be shortly 
> will be available as part of AOSP release, till that time not sure can 
> share user space code outside or not.
> Still if you think need the user space code required to evaluate driver 
> part will check internally and come back on this.

For obvious reasons, we can not take kernel drivers that add a custom
user/kernel api without any userspace code that we can see to use it.
You wouldn't want us to take such code anyway.

So please, fix that, otherwise this is not going to go very far at all.

thanks,

greg k-h