tmakin/ack-tegra
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ANDROID: ashmem: fix up vm_flags direct access which is not allowed anymore

Browse Source 
Commit 1c71222e5f ("mm: replace vma->vm_flags direct modifications
with modifier calls") removed the ability to directly access vm_flags, but
provided wrapper functions to do the task instead.  Use vm_flags_clear()
to fix the build breakage in the ashmem code because of this change.

Fixes: 1c71222e5f ("mm: replace vma->vm_flags direct modifications with modifier calls")
Cc: Suren Baghdasaryan <surenb@google.com>
Change-Id: I865469c1eacd8d037eaaa85eca65e54f717e8706
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
This commit is contained in:
Greg Kroah-Hartman
2023-04-05 13:36:46 +00:00
committed by Treehugger Robot
parent fc97cf1bd0
commit 78ffde117c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
drivers/staging/android/ashmem.c
+1 -1
View File
@@ -401,7 +401,7 @@ static int ashmem_mmap(struct file *file, struct vm_area_struct *vma)
ret = -EPERM;
goto out;
}
vma->vm_flags &= ~calc_vm_may_flags(~asma->prot_mask);
vm_flags_clear(vma, calc_vm_may_flags(~asma->prot_mask));
if (!asma->file) {
char *name = ASHMEM_NAME_DEF;