This is a note to let you know that I've just added the patch titled
Staging: android: binder: Allow using highmem for binder buffers
to the 3.6-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
staging-android-binder-allow-using-highmem-for-binder-buffers.patch
and it can be found in the queue-3.6 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 585650dcec88e704a19bb226a34b6a7166111623 Mon Sep 17 00:00:00 2001
From: Arve Hjønnevåg <[email protected]>
Date: Tue, 16 Oct 2012 15:29:55 -0700
Subject: Staging: android: binder: Allow using highmem for binder buffers
From: Arve Hjønnevåg <[email protected]>
commit 585650dcec88e704a19bb226a34b6a7166111623 upstream.
The default kernel mapping for the pages allocated for the binder
buffers is never used. Set the __GFP_HIGHMEM flag when allocating
these pages so we don't needlessly use low memory pages that may
be required elsewhere.
Signed-off-by: Arve Hjønnevåg <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/staging/android/binder.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/staging/android/binder.c
+++ b/drivers/staging/android/binder.c
@@ -655,7 +655,7 @@ static int binder_update_page_range(stru
page = &proc->pages[(page_addr - proc->buffer) / PAGE_SIZE];
BUG_ON(*page);
- *page = alloc_page(GFP_KERNEL | __GFP_ZERO);
+ *page = alloc_page(GFP_KERNEL | __GFP_HIGHMEM | __GFP_ZERO);
if (*page == NULL) {
pr_err("binder: %d: binder_alloc_buf failed "
"for page at %p\n", proc->pid, page_addr);
Patches currently in stable-queue which might be from [email protected] are
queue-3.6/staging-android-binder-allow-using-highmem-for-binder-buffers.patch
queue-3.6/staging-android-binder-fix-memory-leak-on-thread-process-exit.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
