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: be83bbf806
(mmap: introduce sane default mmap limits)
Signed-off-by: Dave Airlie <airlied@redhat.com>
This commit is contained in:
parent
67b8d5c708
commit
76ef6b28ea
|
@ -212,6 +212,7 @@ static int drm_open_helper(struct file *filp, struct drm_minor *minor)
|
||||||
return -ENOMEM;
|
return -ENOMEM;
|
||||||
|
|
||||||
filp->private_data = priv;
|
filp->private_data = priv;
|
||||||
|
filp->f_mode |= FMODE_UNSIGNED_OFFSET;
|
||||||
priv->filp = filp;
|
priv->filp = filp;
|
||||||
priv->pid = get_pid(task_pid(current));
|
priv->pid = get_pid(task_pid(current));
|
||||||
priv->minor = minor;
|
priv->minor = minor;
|
||||||
|
|
Loading…
Reference in New Issue