Here are the main IOCTLs that used to require root. Now they are
restricted to the first process that opens the DRM device. Of couse
that process may not be an Xserver.

Can people add notes about possible security problems with each of these?

DRM_IOCTL_IRQ_BUSID
DRM_IOCTL_SET_VERSION
DRM_IOCTL_SET_UNIQUE
DRM_IOCTL_BLOCK
DRM_IOCTL_UNBLOCK
DRM_IOCTL_AUTH_MAGIC
DRM_IOCTL_ADD_MAP - still does in most cases
DRM_IOCTL_SET_SAREA_CTX
DRM_IOCTL_ADD_CTX
DRM_IOCTL_RM_CTX
DRM_IOCTL_MOD_CTX
DRM_IOCTL_SWITCH_CTX
DRM_IOCTL_NEW_CTX
DRM_IOCTL_ADD_DRAW
DRM_IOCTL_RM_DRAW
DRM_IOCTL_ADD_BUFS
DRM_IOCTL_MARK_BUFS
DRM_IOCTL_CONTROL
DRM_IOCTL_AGP_ACQUIRE
DRM_IOCTL_AGP_RELEASE
DRM_IOCTL_AGP_ENABLE
DRM_IOCTL_AGP_ALLOC
DRM_IOCTL_AGP_FREE
DRM_IOCTL_AGP_BIND
DRM_IOCTL_AGP_UNBIND
DRM_IOCTL_SG_ALLOC
DRM_IOCTL_SG_FREE


-- 
Jon Smirl
[EMAIL PROTECTED]


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to