From: Todd Kjos <tkjos@google.com>
To: syzbot <syzbot+f9f3f388440283da2965@syzkaller.appspotmail.com>
Cc: "Arve Hjønnevåg" <arve@android.com>,
"Christian Brauner" <christian@brauner.io>,
"open list:ANDROID DRIVERS" <devel@driverdev.osuosl.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
LKML <linux-kernel@vger.kernel.org>,
"Martijn Coenen" <maco@android.com>,
syzkaller-bugs@googlegroups.com, "Todd Kjos" <tkjos@android.com>
Subject: Re: kernel BUG at drivers/android/binder_alloc.c:LINE! (3)
Date: Thu, 28 Mar 2019 13:01:05 -0700 [thread overview]
Message-ID: <CAHRSSEzGaZw4y4gKzyJzxmrkL20NpTAtB8mDeDs+JzsTWeDZKA@mail.gmail.com> (raw)
In-Reply-To: <000000000000de91f105852c8924@google.com>
On Thu, Mar 28, 2019 at 12:27 PM syzbot
<syzbot+f9f3f388440283da2965@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot tried to test the proposed patch but build/boot failed:
>
> patch is already applied
>
>
> Tested on:
>
> commit: 0532a1b0 virt: vbox: Implement passing requestor info to t..
> git tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> char-misc-linus
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> patch: https://syzkaller.appspot.com/x/patch.diff?x=1577678b200000
>
Trying again without (redundantly) attaching the patch...
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
char-misc-linus
next prev parent reply other threads:[~2019-03-28 20:01 UTC|newest]
Thread overview: 12+ 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 [this message]
2019-03-29 0:20 ` syzbot
2019-03-29 0:59 ` Todd Kjos
2019-03-29 9:55 ` syzbot
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 ` 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=CAHRSSEzGaZw4y4gKzyJzxmrkL20NpTAtB8mDeDs+JzsTWeDZKA@mail.gmail.com \
--to=tkjos@google.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=syzbot+f9f3f388440283da2965@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).