All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e113a0b970b7b3f394ba@syzkaller.appspotmail.com>
To: arve@android.com, christian@brauner.io,
	devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
	jannh@google.com, joel@joelfernandes.org,
	linux-kernel@vger.kernel.org, maco@android.com,
	syzkaller-bugs@googlegroups.com, tkjos@android.com,
	tkjos@google.com
Subject: Re: WARNING in binder_transaction_buffer_release (2)
Date: Thu, 06 Aug 2020 04:19:04 -0700	[thread overview]
Message-ID: <000000000000ecb92805ac33a761@google.com> (raw)
In-Reply-To: <0000000000006925ea05a69d5bfb@google.com>

syzbot suspects this issue was fixed by commit:

commit 4b836a1426cb0f1ef2a6e211d7e553221594f8fc
Author: Jann Horn <jannh@google.com>
Date:   Mon Jul 27 12:04:24 2020 +0000

    binder: Prevent context manager from incrementing ref 0

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10c84dec900000
start commit:   9cb1fd0e Linux 5.7-rc7
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=cca7550d53ffa599
dashboard link: https://syzkaller.appspot.com/bug?extid=e113a0b970b7b3f394ba
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1230353c100000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17fd535e100000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: binder: Prevent context manager from incrementing ref 0

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2020-08-06 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27  8:54 WARNING in binder_transaction_buffer_release (2) syzbot
2020-08-06 11:19 ` syzbot [this message]
2020-08-06 16:08   ` Jann Horn
2020-08-06 16:14     ` Todd Kjos

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=000000000000ecb92805ac33a761@google.com \
    --to=syzbot+e113a0b970b7b3f394ba@syzkaller.appspotmail.com \
    --cc=arve@android.com \
    --cc=christian@brauner.io \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --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.