From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: L2CAP: Fix accepting connection request for invalid SPSM
Date: Tue, 01 Nov 2022 20:50:16 +0000 [thread overview]
Message-ID: <166733581629.15990.15999727575150425079.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221031231033.2718204-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 31 Oct 2022 16:10:32 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> The Bluetooth spec states that the valid range for SPSM is from
> 0x0001-0x00ff so it is invalid to accept values outside of this range:
>
> BLUETOOTH CORE SPECIFICATION Version 5.3 | Vol 3, Part A
> page 1059:
> Table 4.15: L2CAP_LE_CREDIT_BASED_CONNECTION_REQ SPSM ranges
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: L2CAP: Fix accepting connection request for invalid SPSM
https://git.kernel.org/bluetooth/bluetooth-next/c/a0978378c152
- [2/2] Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm
https://git.kernel.org/bluetooth/bluetooth-next/c/6bdbca3c41e4
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:[~2022-11-01 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 23:10 [PATCH 1/2] Bluetooth: L2CAP: Fix accepting connection request for invalid SPSM Luiz Augusto von Dentz
2022-10-31 23:10 ` [PATCH 2/2] Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm Luiz Augusto von Dentz
2022-11-01 0:13 ` [1/2] Bluetooth: L2CAP: Fix accepting connection request for invalid SPSM bluez.test.bot
2022-11-01 18:57 ` [PATCH 1/2] " Tedd Ho-Jeong An
2022-11-01 20:50 ` 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=166733581629.15990.15999727575150425079.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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