From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] emulator: bthost: don't crash on ecred_conn_req with too many scid
Date: Mon, 31 Aug 2026 17:30:06 +0000 [thread overview]
Message-ID: <178819740690.676143.15400942592099081045.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <fab8ccab695b50d726bdc00423d8ca915edcf11e.1788043574.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 30 Aug 2026 01:47:58 +0300 you wrote:
> l2cap_ecred_conn_req() crashes if the request contains more SCID than
> specification allows (5).
>
> Respond 0x000C - All connections refused – invalid parameters to such
> invalid requests.
> ---
> emulator/bthost.c | 7 +++++++
> 1 file changed, 7 insertions(+)
Here is the summary with links:
- [BlueZ,1/2] emulator: bthost: don't crash on ecred_conn_req with too many scid
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c53a16afa33d
- [BlueZ,2/2] tools/l2cap-tester: add test for too many ECRED deferred sockets
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0b66bd5335d0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-31 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 22:47 [PATCH BlueZ 1/2] emulator: bthost: don't crash on ecred_conn_req with too many scid Pauli Virtanen
2026-08-29 22:47 ` [PATCH BlueZ 2/2] tools/l2cap-tester: add test for too many ECRED deferred sockets Pauli Virtanen
2026-08-30 1:30 ` [BlueZ,1/2] emulator: bthost: don't crash on ecred_conn_req with too many scid bluez.test.bot
2026-08-31 17:30 ` patchwork-bot+bluetooth [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=178819740690.676143.15400942592099081045.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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