Messages in this thread Patch in this message | | | Date | Fri, 10 Feb 2012 14:47:53 -0800 | From | Greg KH <> | Subject | [14/21] Staging: android: binder: Dont call dump_stack in binder_vma_open |
| |
2.6.32-longterm review patch. If anyone has any objections, please let me know.
------------------
From: Arve HjÞnnevåg <arve@android.com>
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>
--- drivers/staging/android/binder.c | 1 - 1 file changed, 1 deletion(-)
--- a/drivers/staging/android/binder.c +++ b/drivers/staging/android/binder.c @@ -2741,7 +2741,6 @@ static void binder_vma_open(struct vm_ar 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)
| |