linux/include
David Herrmann 3cb01a9804 drm: don't de-authenticate clients on master-close
If an active DRM-Master closes its device, we deauthenticate all clients
on that master. However, if an inactive DRM-Master closes its device, we
do nothing. This is quite inconsistent and breaks several scenarios:

 1) If this was used as security mechanism, it fails horribly if a master
    closes a device while VT switched away. Furthermore, none of the few
    drivers using ->master_*() callbacks seems to require it, anyway.

 2) If you spawn weston (or any other non-UMS compositor) in background
    while another compositor is active, both will get assigned to the
    same "drm_master" object. If the foreground compositor now exits, all
    clients of both the foreground AND background compositor will be
    de-authenticated leading to unexpected behavior.

Stop this non-sense and keep clients authenticated. We don't do this when
dropping DRM-Master (i.e., switching VTs) so don't do it on active-close
either!

Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
2014-08-05 16:07:55 +02:00
..
acpi
asm-generic
clocksource
crypto
drm drm: don't de-authenticate clients on master-close 2014-08-05 16:07:55 +02:00
dt-bindings Two regression fixes for omaps and one fix for device signaling: 2014-07-24 14:06:33 +02:00
keys
kvm
linux Linux 3.16 2014-08-05 09:04:59 +10:00
math-emu
media
memory
misc
net ip: make IP identifiers less predictable 2014-07-28 18:46:34 -07:00
pcmcia
ras
rdma
rxrpc
scsi
sound
target
trace
uapi Linux 3.16 2014-08-05 09:04:59 +10:00
video drm/exynos: fimd: support LCD I80 interface 2014-08-03 16:52:15 +09:00
xen Fix BUG when trying to expand the grant table. This seems to occur 2014-07-30 09:00:20 -07:00
Kbuild