diff options
| author | Dave Airlie <airlied@redhat.com> | 2014-01-14 00:55:36 (GMT) |
|---|---|---|
| committer | Dave Airlie <airlied@redhat.com> | 2014-01-14 00:55:36 (GMT) |
| commit | faf096ffba2b1a4066e6d6dcd1243cc5f3d1fb23 (patch) | |
| tree | 4793c625d9eaae10f453b8c4d32543de86875402 /mm/mprotect.c | |
| parent | a095c60bd06f204c98527aafd5fda6ef42b53eb5 (diff) | |
| parent | 94844cf06568d9592f985e4bd0b9d759a56043c6 (diff) | |
| download | linux-faf096ffba2b1a4066e6d6dcd1243cc5f3d1fb23.tar.xz | |
Merge tag 'vmwgfx-next-2014-01-13' of git://people.freedesktop.org/~thomash/linux into drm-next
Anyway, nothing big here, Three more code cleanup patches from Rashika
Kheria, and one TTM/vmwgfx patch from me that tightens security around TTM
objects enough for them to opened using prime objects from render nodes:
Previously any client could access a shared buffer using the "name", also
without actually opening it. Now a reference is required, and for render nodes
such a reference is intended to only be obtainable using a prime fd.
vmwgfx-next 2014-01-13 pull request
* tag 'vmwgfx-next-2014-01-13' of git://people.freedesktop.org/~thomash/linux:
drivers: gpu: Mark functions as static in vmwgfx_fence.c
drivers: gpu: Mark functions as static in vmwgfx_buffer.c
drivers: gpu: Mark functions as static in vmwgfx_kms.c
drm/ttm: ttm object security fixes for render nodes
Diffstat (limited to 'mm/mprotect.c')
0 files changed, 0 insertions, 0 deletions