binder: Avoid page memory allocation in high memory
In binder, using GFP_HIGHMEM will result in the allocated memory not to be mapped in the kernel's virtual address space. This prevents the kernel from being capable of directly referring it. Change-Id: I952dbc8ae205e47fa00ddf186ef306903f623367 Signed-off-by: Panchajanya1999 <panchajanya@azure-dev.live> Signed-off-by: Forenche <prahul2003@gmail.com> Signed-off-by: Cyber Knight <cyberknight755@gmail.com> Signed-off-by: Pranav Vashi <neobuddy89@gmail.com> Signed-off-by: Sorayukii <sorayukii69@gmail.com>
This commit is contained in:
parent
f187e78d17
commit
e8745f9c1a
1 changed files with 0 additions and 1 deletions
|
|
@ -262,7 +262,6 @@ static int binder_update_page_range(struct binder_alloc *alloc, int allocate,
|
|||
|
||||
trace_binder_alloc_page_start(alloc, index);
|
||||
page->page_ptr = alloc_page(GFP_KERNEL |
|
||||
__GFP_HIGHMEM |
|
||||
__GFP_ZERO);
|
||||
if (!page->page_ptr) {
|
||||
pr_err("%d: binder_alloc_buf failed for page at %pK\n",
|
||||
|
|
|
|||
Loading…
Reference in a new issue