From: syzbot <syzbot+f9f3f388440283da2965@syzkaller.appspotmail.com>
To: arve@android.com, christian@brauner.io,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
joel@joelfernandes.org, linux-kernel@vger.kernel.org,
maco@android.com, syzkaller-bugs@googlegroups.com,
tkjos@android.com, tkjos@google.com
Subject: Re: kernel BUG at drivers/android/binder_alloc.c:LINE! (3)
Date: Fri, 29 Mar 2019 02:55:01 -0700 [thread overview]
Message-ID: <0000000000001165cb058538aaee@google.com> (raw)
In-Reply-To: <CAHRSSEy3od0-7HMCOjbHprc9ihu3VqkJi1-5OKew0oN-2BcPvA@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+f9f3f388440283da2965@syzkaller.appspotmail.com
Tested on:
commit: 8c2ffd91 Linux 5.1-rc2
git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git master
kernel config: https://syzkaller.appspot.com/x/.config?x=8dcdce25ea72bedf
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=10fed663200000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2019-03-29 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 16:14 kernel BUG at drivers/android/binder_alloc.c:LINE! (3) syzbot
2019-03-28 16:32 ` Todd Kjos
2019-03-28 19:27 ` syzbot
2019-03-28 20:01 ` Todd Kjos
2019-03-29 0:20 ` syzbot
2019-03-29 0:59 ` Todd Kjos
2019-03-29 9:55 ` syzbot [this message]
2019-05-17 10:08 ` Dmitry Vyukov
2019-05-17 15:26 ` Todd Kjos
2019-05-17 15:33 ` Dmitry Vyukov
2019-05-17 17:24 ` Todd Kjos
2019-03-28 23:46 ` [B.A.T.M.A.N.] " syzbot
2019-03-28 23:46 ` syzbot
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=0000000000001165cb058538aaee@google.com \
--to=syzbot+f9f3f388440283da2965@syzkaller.appspotmail.com \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tkjos@android.com \
--cc=tkjos@google.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.