[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000ecb92805ac33a761@google.com>
Date: Thu, 06 Aug 2020 04:19:04 -0700
From: syzbot <syzbot+e113a0b970b7b3f394ba@...kaller.appspotmail.com>
To: arve@...roid.com, christian@...uner.io, devel@...verdev.osuosl.org,
gregkh@...uxfoundation.org, jannh@...gle.com,
joel@...lfernandes.org, linux-kernel@...r.kernel.org,
maco@...roid.com, syzkaller-bugs@...glegroups.com,
tkjos@...roid.com, tkjos@...gle.com
Subject: Re: WARNING in binder_transaction_buffer_release (2)
syzbot suspects this issue was fixed by commit:
commit 4b836a1426cb0f1ef2a6e211d7e553221594f8fc
Author: Jann Horn <jannh@...gle.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
Powered by blists - more mailing lists