From: syzbot <syzbot+81232c4a81a886e2b580@syzkaller.appspotmail.com>
To: 309386628@qq.com, davem@davemloft.net,
dominic.coppola@gatoradeadvert.com, dvyukov@google.com,
edumazet@google.com, hdanton@sina.com, johan.hedberg@gmail.com,
krzysztof.kozlowski@linaro.org, kuba@kernel.org,
linma@zju.edu.cn, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, marcel@holtmann.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, zahiabdelmalak0@gmail.com
Subject: Re: [syzbot] [nfc?] [net?] BUG: corrupted list in nfc_llcp_unregister_device
Date: Sun, 05 Nov 2023 09:34:05 -0800 [thread overview]
Message-ID: <000000000000e197ef06096b2454@google.com> (raw)
In-Reply-To: <0000000000006f759505ee84d8d7@google.com>
syzbot suspects this issue was fixed by commit:
commit b938790e70540bf4f2e653dcd74b232494d06c8f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: Fri Sep 15 20:24:47 2023 +0000
Bluetooth: hci_codec: Fix leaking content of local_codecs
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15cb8f17680000
start commit: e1c04510f521 Merge tag 'pm-6.2-rc9' of git://git.kernel.or..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=fe56f7d193926860
dashboard link: https://syzkaller.appspot.com/bug?extid=81232c4a81a886e2b580
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e90568c80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: hci_codec: Fix leaking content of local_codecs
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-11-05 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 9:53 [syzbot] BUG: corrupted list in nfc_llcp_unregister_device syzbot
2022-12-30 10:41 ` syzbot
2023-11-05 17:34 ` syzbot [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=000000000000e197ef06096b2454@google.com \
--to=syzbot+81232c4a81a886e2b580@syzkaller.appspotmail.com \
--cc=309386628@qq.com \
--cc=davem@davemloft.net \
--cc=dominic.coppola@gatoradeadvert.com \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=johan.hedberg@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--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=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zahiabdelmalak0@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 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).