From: syzbot <syzbot+4ed6852d4da4606c93da@syzkaller.appspotmail.com>
To: ipravdin.official@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] general protection fault in bcsp_recv
Date: Sat, 30 Aug 2025 12:46:03 -0700 [thread overview]
Message-ID: <68b354fb.050a0220.3db4df.01ab.GAE@google.com> (raw)
In-Reply-To: <5e4ppwjfwtg7ruzkgyyke6vwosiro3vj6wm4hic3sjwh5bu7la@fghymhrnubbo>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+4ed6852d4da4606c93da@syzkaller.appspotmail.com
Tested-by: syzbot+4ed6852d4da4606c93da@syzkaller.appspotmail.com
Tested on:
commit: 02925b3b Bluetooth: Fix use-after-free in l2cap_sock_c..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=110b8e34580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c6b2ceaf54a94b5e
dashboard link: https://syzkaller.appspot.com/bug?extid=4ed6852d4da4606c93da
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=10ab2a62580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-08-30 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 17:18 [syzbot] [bluetooth?] general protection fault in bcsp_recv syzbot
2025-04-02 23:56 ` syzbot
2025-06-30 8:03 ` Hillf Danton
2025-06-30 8:39 ` syzbot
2025-06-30 3:03 ` [syzbot] " syzbot
2025-08-27 14:29 ` Forwarded: " syzbot
2025-08-27 14:36 ` syzbot
2025-08-30 18:37 ` Ivan Pravdin
2025-08-30 19:46 ` syzbot [this message]
[not found] <pxrxtntcuuqt5opsno55wx62yqafwhfqkqhylpbwwkqt4iabdv@2nmky356ufdo>
2025-06-30 3:22 ` syzbot
[not found] <nqdjhsx4cy3x64g3q6w6ffczvcwhh7aavelmrvqjtinqetusa4@4xdhtbpkhlse>
2025-08-27 15:11 ` syzbot
[not found] <cdfnb7ox7u3qogpyvxgti4ljpsa7ohvh2ilzy2tqygzsvxmh3a@cglm7naoohg5>
2025-08-27 15:49 ` 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=68b354fb.050a0220.3db4df.01ab.GAE@google.com \
--to=syzbot+4ed6852d4da4606c93da@syzkaller.appspotmail.com \
--cc=ipravdin.official@gmail.com \
--cc=linux-kernel@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.