Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH 1/2] Bluetooth: L2CAP: Fix accepting connection request for
 invalid SPSM
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <166733581629.15990.15999727575150425079.git-patchwork-notify@kernel.org>
Date:   Tue, 01 Nov 2022 20:50:16 +0000
References: <20221031231033.2718204-1-luiz.dentz@gmail.com>
In-Reply-To: <20221031231033.2718204-1-luiz.dentz@gmail.com>
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org
Precedence: bulk

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