From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752456AbdHHRet (ORCPT ); Tue, 8 Aug 2017 13:34:49 -0400 Received: from mail-qt0-f180.google.com ([209.85.216.180]:36335 "EHLO mail-qt0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752129AbdHHRes (ORCPT ); Tue, 8 Aug 2017 13:34:48 -0400 MIME-Version: 1.0 In-Reply-To: <20170728115608.61306-4-maco@android.com> References: <20170728115608.61306-1-maco@android.com> <20170728115608.61306-4-maco@android.com> From: John Stultz Date: Tue, 8 Aug 2017 10:34:47 -0700 Message-ID: Subject: Re: [PATCH 3/3] ANDROID: binder: fix proc->tsk check. To: Martijn Coenen Cc: Greg KH , Todd Kjos , =?UTF-8?B?QXJ2ZSBIasO4bm5ldsOlZw==?= , Amit Pundir , lkml , devel@driverdev.osuosl.org, Martijn Coenen Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 28, 2017 at 4:56 AM, Martijn Coenen wrote: > Commit c4ea41ba195d ("binder: use group leader instead of open thread")' > was incomplete and didn't update a check in binder_mmap(), causing all > mmap() calls into the binder driver to fail. > > Signed-off-by: Martijn Coenen > --- > drivers/android/binder.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/android/binder.c b/drivers/android/binder.c > index f7665c31feca..831cdd7d197d 100644 > --- a/drivers/android/binder.c > +++ b/drivers/android/binder.c > @@ -3362,7 +3362,7 @@ static int binder_mmap(struct file *filp, struct vm_area_struct *vma) > const char *failure_string; > struct binder_buffer *buffer; > > - if (proc->tsk != current) > + if (proc->tsk != current->group_leader) > return -EINVAL; > > if ((vma->vm_end - vma->vm_start) > SZ_4M) Tested-by: John Stultz As Amit already confirmed, this resolves the wifi and bluetooth regression I was seeing with Android using 4.13-rc2. Though I've not seen it show up in Linus' tree yet, so I wanted to pester folks so it gets into 4.13-rc (its given me some slight grief trying to bisect down a separate issue). thanks -john