summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorArve Hjønnevåg <arve@android.com>2012-01-20 19:56:21 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-02-13 11:28:50 -0800
commit038044951a5b58411446428629594e67320549e5 (patch)
treedf4a888862bb45c4ea3f8416b3008f26b97d1506
parent76058ae1c7386da3de3ad6ebd8fce5d4fc5ae59d (diff)
downloadlwn-038044951a5b58411446428629594e67320549e5.tar.gz
lwn-038044951a5b58411446428629594e67320549e5.zip
Staging: android: binder: Don't call dump_stack in binder_vma_open
commit 3c1b86f17068cf6476fb2d022b9c8b44dedea2e5 upstream. If user-space partially unmaps the driver, binder_vma_open would dump the kernel stack. This is not a kernel bug however and will be treated as if the whole area was unmapped once binder_vma_close gets called. Signed-off-by: Arve Hjønnevåg <arve@android.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r--drivers/staging/android/binder.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/staging/android/binder.c b/drivers/staging/android/binder.c
index 99010d4b3044..61576a206ea7 100644
--- a/drivers/staging/android/binder.c
+++ b/drivers/staging/android/binder.c
@@ -2741,7 +2741,6 @@ static void binder_vma_open(struct vm_area_struct *vma)
proc->pid, vma->vm_start, vma->vm_end,
(vma->vm_end - vma->vm_start) / SZ_1K, vma->vm_flags,
(unsigned long)pgprot_val(vma->vm_page_prot));
- dump_stack();
}
static void binder_vma_close(struct vm_area_struct *vma)