Re: [CFR][PATCH] drm2: don't assume that dev-driver-max_ioctl *dev-driver-compat_ioctls_nr

2014-11-29 Thread Eygene Ryabinkin
Fri, Nov 28, 2014 at 07:32:26PM +0200, Konstantin Belousov wrote: On Fri, Nov 28, 2014 at 04:29:42PM +0300, Eygene Ryabinkin wrote: I noticed that the current ioctl processing code for drm2 implicitely assumes that the number of native ioctls is higher than that of 32-bit compat ones, so it

[CFR][PATCH] drm2: don't assume that dev-driver-max_ioctl *dev-driver-compat_ioctls_nr

2014-11-28 Thread Eygene Ryabinkin
Konstantin, *, good day. I noticed that the current ioctl processing code for drm2 implicitely assumes that the number of native ioctls is higher than that of 32-bit compat ones, so it immediately gives EINVAL when nr = dev-driver-max_ioctl. Seems that in future such assumption may not be true

Re: [CFR][PATCH] drm2: don't assume that dev-driver-max_ioctl *dev-driver-compat_ioctls_nr

2014-11-28 Thread Konstantin Belousov
On Fri, Nov 28, 2014 at 04:29:42PM +0300, Eygene Ryabinkin wrote: Konstantin, *, good day. I noticed that the current ioctl processing code for drm2 implicitely assumes that the number of native ioctls is higher than that of 32-bit compat ones, so it immediately gives EINVAL when nr =