From: syzbot <syzbot+77e5e02c6c81136cdaff@syzkaller.appspotmail.com>
To: Markus.Elfring@web.de, anant.thazhemadam@gmail.com,
davem@davemloft.net, gregkh@linuxfoundation.org,
hdanton@sina.com, 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
Subject: Re: [syzbot] KASAN: use-after-free Read in __queue_work (3)
Date: Thu, 13 May 2021 09:27:04 -0700 [thread overview]
Message-ID: <000000000000fd05a005c2389844@google.com> (raw)
In-Reply-To: <000000000000aaa4a905ac646223@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=127b3593d00000
start commit: c0842fbc random32: move the pseudo-random 32-bit definitio..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=cf567e8c7428377e
dashboard link: https://syzkaller.appspot.com/bug?extid=77e5e02c6c81136cdaff
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=140e36a4900000
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-13 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 21:27 KASAN: use-after-free Read in __queue_work (3) syzbot
2021-05-13 16:27 ` syzbot [this message]
2021-05-14 7:50 ` [syzbot] " Dmitry Vyukov
2024-09-06 10:40 ` [syzbot] syzbot
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=000000000000fd05a005c2389844@google.com \
--to=syzbot+77e5e02c6c81136cdaff@syzkaller.appspotmail.com \
--cc=Markus.Elfring@web.de \
--cc=anant.thazhemadam@gmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--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 \
/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.