summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/vgem/vgem_fence.c
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2020-07-08 18:49:11 +0300
committerChris Wilson <chris@chris-wilson.co.uk>2020-07-09 00:00:21 +0300
commit119c53d2d4044c59c450c4f5a568d80b9d861856 (patch)
treeb7871f380b65f0bfb5621471f858b7dbac73af2a /drivers/gpu/drm/vgem/vgem_fence.c
parentebd267b2e3c25d5f93a08528b47c036569eb8744 (diff)
downloadlinux-119c53d2d4044c59c450c4f5a568d80b9d861856.tar.xz
drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
drm_gem_dumb_map_offset() now exists and does everything vgem_gem_dump_map does and *ought* to do. In particular, vgem_gem_dumb_map() was trying to reject mmapping an imported dmabuf by checking the existence of obj->filp. Unfortunately, we always allocated an obj->filp, even if unused for an imported dmabuf. Instead, the drm_gem_dumb_map_offset(), since commit 90378e589192 ("drm/gem: drm_gem_dumb_map_offset(): reject dma-buf"), uses the obj->import_attach to reject such invalid mmaps. This prevents vgem from allowing userspace mmapping the dumb handle and attempting to incorrectly fault in remote pages belonging to another device, where there may not even be a struct page. v2: Use the default drm_gem_dumb_map_offset() callback Fixes: af33a9190d02 ("drm/vgem: Enable dmabuf import interfaces") Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: <stable@vger.kernel.org> # v4.13+ Link: https://patchwork.freedesktop.org/patch/msgid/20200708154911.21236-1-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/vgem/vgem_fence.c')
0 files changed, 0 insertions, 0 deletions