From: Arve Hjønnevåg Date: Sat, 21 Jan 2012 03:56:21 +0000 (-0800) Subject: Staging: android: binder: Don't call dump_stack in binder_vma_open X-Git-Tag: upstream/snapshot3+hdmi~8168^2~15 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3c1b86f17068cf6476fb2d022b9c8b44dedea2e5;p=platform%2Fadaptation%2Frenesas_rcar%2Frenesas_kernel.git Staging: android: binder: Don't call dump_stack in binder_vma_open 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)