drm: make buffer management work without DRM_MASTER
commitfb30edf5e4b43745f33a1df5fec32721f63026c2
authorDavid Herrmann <dh.herrmann@googlemail.com>
Tue, 11 Sep 2012 18:35:11 +0000 (11 18:35 +0000)
committerDave Airlie <airlied@redhat.com>
Thu, 13 Sep 2012 01:19:44 +0000 (13 11:19 +1000)
tree108330c0acfabe0c727e14601ec512a238554e7c
parent95ca19cf8cbf6163805dc9dc6a83f73b3e75ea13
drm: make buffer management work without DRM_MASTER

DRM users should be able to create/destroy/manage dumb- and frame-buffers
without DRM_MASTER. These ioctls do not affect modesetting so there is no
reason to protect them by drm-master. Particularly, destroying buffers
should always be possible as a client has only access to buffers that they
created. Hence, there is no reason to prevent a client from destroying the
buffers, considering a simple close() would destroy them, anyway.

Furthermore, a display-server currently cannot shutdown correctly if it
does not have DRM_MASTER. If some other display-server becomes active (or
the kernel console), then the background display-server is unable to
destroy its buffers.
Under special curcumstances (like monitor reconfiguration) this might even
happen during runtime.

Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
drivers/gpu/drm/drm_drv.c