From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+2e9900a1e1b3c9c96a77@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: WARNING: refcount bug in do_enable_set
Date: Wed, 11 Nov 2020 14:11:02 +0100 [thread overview]
Message-ID: <CACT4Y+bJevNFi6P9kYEEQshTuNhpzLyHL1Q_NatjyS90dMHwqw@mail.gmail.com> (raw)
In-Reply-To: <000000000000a3de6505ae9e6831@google.com>
On Sun, Sep 6, 2020 at 7:31 AM syzbot
<syzbot+2e9900a1e1b3c9c96a77@syzkaller.appspotmail.com> wrote:
>
> 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=115a4245900000
> 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=226c7a97d80bec54
> dashboard link: https://syzkaller.appspot.com/bug?extid=2e9900a1e1b3c9c96a77
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12b3efea900000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11131284900000
>
> 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
#syz fix: Bluetooth: Fix kernel oops triggered by hci_adv_monitors_clear()
prev parent reply other threads:[~2020-11-11 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 6:44 WARNING: refcount bug in do_enable_set syzbot
2020-08-02 14:58 ` syzbot
2020-09-06 5:31 ` syzbot
2020-11-11 13:11 ` Dmitry Vyukov [this message]
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=CACT4Y+bJevNFi6P9kYEEQshTuNhpzLyHL1Q_NatjyS90dMHwqw@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2e9900a1e1b3c9c96a77@syzkaller.appspotmail.com \
--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 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).