drm: set FMODE_UNSIGNED_OFFSET for drm files
authorDave Airlie <airlied@redhat.com>
Tue, 15 May 2018 03:38:15 +0000 (13:38 +1000)
committerDave Airlie <airlied@redhat.com>
Tue, 15 May 2018 04:46:04 +0000 (14:46 +1000)
commit76ef6b28ea4f81c3d511866a9b31392caa833126
treea6523e611696a5b7422cfbf04ed9c0ba3d798c42
parent67b8d5c7081221efa252e111cd52532ec6d4266f
drm: set FMODE_UNSIGNED_OFFSET for drm files

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>
drivers/gpu/drm/drm_file.c