From: syzbot <syzbot+cf54c1da6574b6c1b049@syzkaller.appspotmail.com>
To: linux-bluetooth@vger.kernel.org, pav@iki.fi,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in sco_chan_del
Date: Sat, 19 Aug 2023 07:01:25 -0700 [thread overview]
Message-ID: <000000000000b998c106034714cb@google.com> (raw)
In-Reply-To: <d5aebbd4337291708c970380fa947a0fe1767cd5.1692451565.git.pav@iki.fi>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+cf54c1da6574b6c1b049@syzkaller.appspotmail.com
Tested on:
commit: f0835e74 Bluetooth: ISO: Use defer setup to separate P..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1479e265a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4b3a4035b595be0
dashboard link: https://syzkaller.appspot.com/bug?extid=cf54c1da6574b6c1b049
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=13b9e265a80000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2023-08-19 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 13:33 [PATCH] Bluetooth: hci_conn: fail SCO/ISO via hci_conn_failed if ACL gone early Pauli Virtanen
2023-08-19 14:01 ` bluez.test.bot
2023-08-19 14:01 ` syzbot [this message]
2023-08-21 20:40 ` [PATCH] " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-05-15 12:47 [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in sco_chan_del syzbot
2023-05-15 16:01 ` Ruihan Li
2023-08-17 12:56 ` syzbot
2023-08-18 4:39 ` 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=000000000000b998c106034714cb@google.com \
--to=syzbot+cf54c1da6574b6c1b049@syzkaller.appspotmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
--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