From: syzbot <syzbot+a41dfef1d2e04910eb2e@syzkaller.appspotmail.com>
To: a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
bobo.shaobowang@huawei.com, davem@davemloft.net,
hdanton@sina.com, johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, marcel@holtmann.org,
mareklindner@neomailbox.ch, miklos@szeredi.hu,
mszeredi@redhat.com, netdev@vger.kernel.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: trying to register non-static key in l2cap_sock_teardown_cb
Date: Tue, 30 Nov 2021 08:19:10 -0800 [thread overview]
Message-ID: <000000000000dc091705d203eac6@google.com> (raw)
In-Reply-To: <000000000000f5964705b7d47d8c@google.com>
syzbot suspects this issue was fixed by commit:
commit 1bff51ea59a9afb67d2dd78518ab0582a54a472c
Author: Wang ShaoBo <bobo.shaobowang@huawei.com>
Date: Wed Sep 1 00:35:37 2021 +0000
Bluetooth: fix use-after-free error in lock_sock_nested()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=134c881eb00000
start commit: 73b7a6047971 net: dsa: bcm_sf2: support BCM4908's integrat..
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=9ce34124da4c882b
dashboard link: https://syzkaller.appspot.com/bug?extid=a41dfef1d2e04910eb2e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=166ee4cf500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1337172f500000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: fix use-after-free error in lock_sock_nested()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-11-30 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 10:49 INFO: trying to register non-static key in l2cap_sock_teardown_cb syzbot
2021-01-10 21:40 ` syzbot
2021-01-11 5:16 ` syzbot
2021-11-30 16:19 ` syzbot [this message]
2021-12-04 9:32 ` [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=000000000000dc091705d203eac6@google.com \
--to=syzbot+a41dfef1d2e04910eb2e@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bobo.shaobowang@huawei.com \
--cc=davem@davemloft.net \
--cc=hdanton@sina.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=mareklindner@neomailbox.ch \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
--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).