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>
Mon, 11 Jun 2018 20:49:22 +0000 (22:49 +0200)
commit2abd4c3ed20df4609c28cefa4df36b3dad9dfed7
tree7c460c3b89138e61bf513cb08baefe4fc2e961f7
parent3fe4b0cf93833af2ef497784bdfb2a4eecaabb6e
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_file.c