summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/omapdrm
diff options
context:
space:
mode:
authorDave Airlie <airlied@redhat.com>2018-05-15 13:38:15 +1000
committerDave Airlie <airlied@redhat.com>2018-05-15 14:46:04 +1000
commit76ef6b28ea4f81c3d511866a9b31392caa833126 (patch)
treea6523e611696a5b7422cfbf04ed9c0ba3d798c42 /drivers/gpu/drm/omapdrm
parent67b8d5c7081221efa252e111cd52532ec6d4266f (diff)
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>
Diffstat (limited to 'drivers/gpu/drm/omapdrm')
0 files changed, 0 insertions, 0 deletions