All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2e9900a1e1b3c9c96a77@syzkaller.appspotmail.com>
To: Markus.Elfring@web.de, abhishekpandit@chromium.org,
	alainm@chromium.org, davem@davemloft.net, hdanton@sina.com,
	johan.hedberg@gmail.com, koulihong@huawei.com, kuba@kernel.org,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	marcel@holtmann.org, mcchou@chromium.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: refcount bug in do_enable_set
Date: Sat, 05 Sep 2020 22:31:07 -0700	[thread overview]
Message-ID: <000000000000a3de6505ae9e6831@google.com> (raw)
In-Reply-To: <0000000000008b9e0705a38afe52@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=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

  parent reply	other threads:[~2020-09-06  5:31 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 [this message]
2020-11-11 13:11   ` 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=000000000000a3de6505ae9e6831@google.com \
    --to=syzbot+2e9900a1e1b3c9c96a77@syzkaller.appspotmail.com \
    --cc=Markus.Elfring@web.de \
    --cc=abhishekpandit@chromium.org \
    --cc=alainm@chromium.org \
    --cc=davem@davemloft.net \
    --cc=hdanton@sina.com \
    --cc=johan.hedberg@gmail.com \
    --cc=koulihong@huawei.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.