public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+55de1eb4975dec156d8f@syzkaller.appspotmail.com>
To: arve@android.com, christian@brauner.io,
	devel@driverdev.osuosl.org, dvyukov@google.com,
	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! (2)
Date: Thu, 14 Feb 2019 14:36:03 -0800	[thread overview]
Message-ID: <00000000000088c7d60581e2483f@google.com> (raw)
In-Reply-To: <CAHRSSEx0ifKf-bA9NGwXak0DhWt6Xfxe+SQgfEEdNcyVAPwb_Q@mail.gmail.com>

Hello,

syzbot tried to test the proposed patch but build/boot failed:

failed to checkout kernel repo  
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/linux-next:  
failed to run  
["git" "fetch" "https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git" "linux-next"]:  
exit status 128
fatal: Couldn't find remote ref linux-next



Tested on:

commit:         [unknown]
git tree:        
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git  
linux-next
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=17832048c00000


  reply	other threads:[~2019-02-14 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 11:31 kernel BUG at drivers/android/binder_alloc.c:LINE! (2) syzbot
2019-02-14 11:35 ` syzbot
2019-02-14 22:34   ` Todd Kjos
2019-02-14 22:36     ` syzbot [this message]
2019-02-14 22:46     ` Todd Kjos
2019-02-14 23:04       ` syzbot
2019-02-15  5:38 ` 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=00000000000088c7d60581e2483f@google.com \
    --to=syzbot+55de1eb4975dec156d8f@syzkaller.appspotmail.com \
    --cc=arve@android.com \
    --cc=christian@brauner.io \
    --cc=devel@driverdev.osuosl.org \
    --cc=dvyukov@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox