From: syzbot <syzbot+0ce8a29c6c6469b16632@syzkaller.appspotmail.com>
To: davem@davemloft.net, gregkh@linuxfoundation.org,
johan.hedberg@gmail.com, kuba@kernel.org, linma@zju.edu.cn,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
syzscope@gmail.com
Subject: Re: [syzbot] WARNING: ODEBUG bug in bt_host_release
Date: Thu, 13 May 2021 23:33:05 -0700 [thread overview]
Message-ID: <000000000000987c8205c2446ac9@google.com> (raw)
In-Reply-To: <0000000000001d48cd05abebd088@google.com>
syzbot suspects this issue was fixed by commit:
commit e2cb6b891ad2b8caa9131e3be70f45243df82a80
Author: Lin Ma <linma@zju.edu.cn>
Date: Mon Apr 12 11:17:57 2021 +0000
bluetooth: eliminate the potential race condition when removing the HCI controller
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15427145d00000
start commit: f873db9a Merge tag 'io_uring-5.9-2020-08-21' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bb68b9e8a8cc842f
dashboard link: https://syzkaller.appspot.com/bug?extid=0ce8a29c6c6469b16632
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10310972900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bluetooth: eliminate the potential race condition when removing the HCI controller
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-05-14 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 21:36 WARNING: ODEBUG bug in bt_host_release syzbot
2021-05-05 0:16 ` SyzScope
2021-05-14 6:33 ` syzbot [this message]
2021-05-14 7:50 ` [syzbot] " 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=000000000000987c8205c2446ac9@google.com \
--to=syzbot+0ce8a29c6c6469b16632@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linma@zju.edu.cn \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzscope@gmail.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.