From: patchwork-bot+bluetooth@kernel.org
To: Dudu Lu <phx0fer@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com
Subject: Re: [PATCH] Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req
Date: Wed, 15 Apr 2026 21:00:06 +0000 [thread overview]
Message-ID: <177628680629.2439002.124743646489985763.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260415104355.76524-1-phx0fer@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 15 Apr 2026 18:43:55 +0800 you wrote:
> The L2CAP specification states that if more than one channel is being
> reconfigured, the MPS shall not be decreased. The current check has
> two issues:
>
> 1) The comparison uses >= (greater-than-or-equal), which incorrectly
> rejects reconfiguration requests where the MPS stays the same.
> Since the spec says MPS "shall be greater than or equal to the
> current MPS", only a strict decrease (remote_mps > mps) should be
> rejected. Keeping the same MPS is valid.
>
> [...]
Here is the summary with links:
- Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req
https://git.kernel.org/bluetooth/bluetooth-next/c/b1de65fd5f81
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-04-15 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 10:43 [PATCH] Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req Dudu Lu
2026-04-15 11:21 ` bluez.test.bot
2026-04-15 21:00 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-13 8:56 [PATCH] Bluetooth: l2cap: Fix " Dudu Lu
2026-04-13 17:16 ` Luiz Augusto von Dentz
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=177628680629.2439002.124743646489985763.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=phx0fer@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