[PATCH 0/7] drm: Sanitize DRM_IOCTL_MODE_CREATE_DUMB input

On Wed, Nov 05, 2014 at 02:24:42PM +, Russell King - ARM Linux wrote: > On Wed, Nov 05, 2014 at 02:25:12PM +0100, Thierry Reding wrote: > > Discussion on IRC lead to the conclusion that new IOCTLs should have > > input validation and require userspace to zero out output parameters to > > avoid

[PATCH 0/7] drm: Sanitize DRM_IOCTL_MODE_CREATE_DUMB input

On Wed, Nov 05, 2014 at 02:24:42PM +, Russell King - ARM Linux wrote: > On Wed, Nov 05, 2014 at 02:25:12PM +0100, Thierry Reding wrote: > > Discussion on IRC lead to the conclusion that new IOCTLs should have > > input validation and require userspace to zero out output parameters to > > avoid

[PATCH 0/7] drm: Sanitize DRM_IOCTL_MODE_CREATE_DUMB input

From: Thierry Reding Drivers currently treat the IOCTL data for DRM_IOCTL_MODE_CREATE_DUMB inconsistently. While the documentation clearly states that the handle, pitch and size fields are outputs, some drivers use their values as a minimum hint from userspace, presumably to

[PATCH 0/7] drm: Sanitize DRM_IOCTL_MODE_CREATE_DUMB input

On Wed, Nov 05, 2014 at 02:25:12PM +0100, Thierry Reding wrote: > Discussion on IRC lead to the conclusion that new IOCTLs should have > input validation and require userspace to zero out output parameters to > avoid this kind of mess in the future. In order to help avoid this kind > of ambiguity