[PATCH] drm: Perform ioctl command validation on the stored kernel values

> ioctl cmd, and for example trinity likes to fuzz those bits to create > conflicting commands. So instead of relying upon userspace to pass along > the correct IN/OUT flags for the ioctl, use the flags as expected by the > kernel. > > This does have a side-effect that NULL pointers can not be subs

Re: [PATCH] drm: Perform ioctl command validation on the stored kernel values

> ioctl cmd, and for example trinity likes to fuzz those bits to create > conflicting commands. So instead of relying upon userspace to pass along > the correct IN/OUT flags for the ioctl, use the flags as expected by the > kernel. > > This does have a side-effect that NULL pointers can not be subs

[PATCH] drm: Perform ioctl command validation on the stored kernel values

Userspace is free to pass in any command bits it feels like through the ioctl cmd, and for example trinity likes to fuzz those bits to create conflicting commands. So instead of relying upon userspace to pass along the correct IN/OUT flags for the ioctl, use the flags as expected by the kernel. Th

[PATCH] drm: Perform ioctl command validation on the stored kernel values

Userspace is free to pass in any command bits it feels like through the ioctl cmd, and for example trinity likes to fuzz those bits to create conflicting commands. So instead of relying upon userspace to pass along the correct IN/OUT flags for the ioctl, use the flags as expected by the kernel. Th