blob: 376f336fad16b29fec5317f542e7e150ee44653b [file] [log] [blame]
From 3c1b86f17068cf6476fb2d022b9c8b44dedea2e5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Arve=20Hj=C3=B8nnev=C3=A5g?= <>
Date: Fri, 20 Jan 2012 19:56:21 -0800
Subject: Staging: android: binder: Don't call dump_stack in
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Patch-mainline: HEAD
Git-commit: 3c1b86f17068cf6476fb2d022b9c8b44dedea2e5
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 <>
Cc: stable <>
Signed-off-by: Greg Kroah-Hartman <>
diff --git a/drivers/staging/android/binder.c b/drivers/staging/android/binder.c
index 7491801..48cf27c 100644
--- a/drivers/staging/android/binder.c
+++ b/drivers/staging/android/binder.c
@@ -2759,7 +2759,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)