From: Carlos Llamas <cmllamas@google.com>
To: syzbot <syzbot+ff47834028a51cf6f857@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, arve@android.com, brauner@kernel.org,
gregkh@linuxfoundation.org, joel@joelfernandes.org,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
maco@android.com, omosnace@redhat.com, surenb@google.com,
syzkaller-bugs@googlegroups.com, tkjos@android.com
Subject: Re: [syzbot] general protection fault in binder_alloc_new_buf_locked
Date: Fri, 2 Sep 2022 15:53:23 +0000 [thread overview]
Message-ID: <YxIm8/d293sSuECc@google.com> (raw)
In-Reply-To: <000000000000ae694805e7b2bda3@google.com>
On Fri, Sep 02, 2022 at 07:42:36AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: b90cb1053190 Linux 6.0-rc3
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=1719e383080000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9c5c41fc03fda66f
> dashboard link: https://syzkaller.appspot.com/bug?extid=ff47834028a51cf6f857
> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11794975080000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1445c063080000
>
> The issue was bisected to:
>
> commit 44e602b4e52f70f04620bbbf4fe46ecb40170bde
> Author: Liam Howlett <liam.howlett@oracle.com>
> Date: Wed Aug 10 16:02:25 2022 +0000
>
> binder_alloc: add missing mmap_lock calls when using the VMA
>
Duplicate report, this time bisection worked though.
#syz dup: general protection fault in binder_alloc_new_buf
prev parent reply other threads:[~2022-09-02 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 14:42 [syzbot] general protection fault in binder_alloc_new_buf_locked syzbot
2022-09-02 15:53 ` Carlos Llamas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YxIm8/d293sSuECc@google.com \
--to=cmllamas@google.com \
--cc=akpm@linux-foundation.org \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=omosnace@redhat.com \
--cc=surenb@google.com \
--cc=syzbot+ff47834028a51cf6f857@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tkjos@android.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.