Re: [PATCH v2 05/17] compat_ioctl: move more drivers to generic_compat_ioctl_ptrarg
From: Al Viro <viro@ZenIV.linux.org.uk>
Date: 2018-09-14 20:57:48
Also in:
amd-gfx, ceph-devel, dri-devel, linux-btrfs, linux-crypto, linux-fbdev, linux-fsdevel, linux-iio, linux-input, linux-media, linux-pci, linux-rdma, linux-remoteproc, linux-scsi, linux-usb, linuxppc-dev, lkml, netdev, nvdimm, platform-driver-x86, sparclinux
On Fri, Sep 14, 2018 at 01:35:06PM -0700, Darren Hart wrote:
Acked-by: Darren Hart (VMware) <dvhart@infradead.org> As for a longer term solution, would it be possible to init fops in such a way that the compat_ioctl call defaults to generic_compat_ioctl_ptrarg so we don't have to duplicate this boilerplate for every ioctl fops structure?
Bad idea, that... Because several years down the road somebody will add an ioctl that takes an unsigned int for argument. Without so much as looking at your magical mystery macro being used to initialize file_operations. FWIW, I would name that helper in more blunt way - something like compat_ioctl_only_compat_pointer_ioctls_here()...