From: syzbot <syzbot+198362c76088d1515529@syzkaller.appspotmail.com>
To: abhishekpandit@chromium.org, alainm@chromium.org,
bliniob53@gmail.com, davem@davemloft.net,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org, mcchou@chromium.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: refcount bug in l2cap_chan_put
Date: Sat, 05 Sep 2020 18:07:05 -0700 [thread overview]
Message-ID: <0000000000005fc62d05ae9ab8c2@google.com> (raw)
In-Reply-To: <0000000000000cce30059f4e27e9@google.com>
syzbot suspects this issue was fixed by commit:
commit b83764f9220a4a14525657466f299850bbc98de9
Author: Miao-chen Chou <mcchou@chromium.org>
Date: Tue Jun 30 03:15:00 2020 +0000
Bluetooth: Fix kernel oops triggered by hci_adv_monitors_clear()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11aaff5d900000
start commit: fffe3ae0 Merge tag 'for-linus-hmm' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=18bb86f2e4ebfda2
dashboard link: https://syzkaller.appspot.com/bug?extid=198362c76088d1515529
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=152a482c900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=109b781a900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: Fix kernel oops triggered by hci_adv_monitors_clear()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-06 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 8:28 WARNING: refcount bug in l2cap_chan_put syzbot
2020-02-24 19:32 ` Abhishek Pandit-Subedi
2020-02-25 1:18 ` Luiz Augusto von Dentz
2020-02-25 6:29 ` Marcel Holtmann
2020-09-06 1:07 ` syzbot [this message]
2020-11-11 13:26 ` Dmitry Vyukov
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=0000000000005fc62d05ae9ab8c2@google.com \
--to=syzbot+198362c76088d1515529@syzkaller.appspotmail.com \
--cc=abhishekpandit@chromium.org \
--cc=alainm@chromium.org \
--cc=bliniob53@gmail.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mcchou@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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.