drm: set FMODE_UNSIGNED_OFFSET for drm files
authorDave Airlie <airlied@redhat.com>
Tue, 15 May 2018 03:38:15 +0000 (13:38 +1000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 13 Jun 2018 14:16:41 +0000 (16:16 +0200)
commit8655f2847fd5d52fc22ed2d1ce00e801ab6a77c2
tree740073f9fc99f3d99913423ba7d67cfda99bbfe6
parent1ec1dfba0835308ef3119fdc8be01c610da0b035
drm: set FMODE_UNSIGNED_OFFSET for drm files

commit 76ef6b28ea4f81c3d511866a9b31392caa833126 upstream.

Since we have the ttm and gem vma managers using a subset
of the file address space for objects, and these start at
0x100000000 they will overflow the new mmap checks.

I've checked all the mmap routines I could see for any
bad behaviour but overall most people use GEM/TTM VMA
managers even the legacy drivers have a hashtable.

Reported-and-Tested-by: Arthur Marsh (amarsh04 on #radeon)
Fixes: be83bbf8068 (mmap: introduce sane default mmap limits)
Signed-off-by: Dave Airlie <airlied@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/gpu/drm/drm_fops.c