All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Joas Antonio dos Santos <joasantonio108@gmail.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bluetooth-next v2] Bluetooth: L2CAP: validate MPS and MTU in ECRED connection response
Date: Tue, 10 Nov 2026 16:10:12 +0000	[thread overview]
Message-ID: <179432701267.4062787.11305401861516612930.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110-bt-ecred-mps-fix-v2-1-48c5ee28fd8a@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 10 Nov 2026 03:26:03 +0000 you wrote:
> From: Joas Antonio dos Santos <joasantonio108@gmail.com>
> 
> l2cap_ecred_conn_rsp() stores the MTU and MPS from the peer without
> checking them against the minimums required for enhanced credit based
> channels.  The other LE and ECRED handlers (l2cap_le_connect_req(),
> l2cap_le_connect_rsp(), l2cap_ecred_conn_req(), l2cap_ecred_reconf_req())
> all reject values below the minimum.
> 
> [...]

Here is the summary with links:
  - [bluetooth-next,v2] Bluetooth: L2CAP: validate MPS and MTU in ECRED connection response
    https://git.kernel.org/bluetooth/bluetooth-next/c/1645edfa8c29

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-10 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  3:26 [PATCH bluetooth-next v2] Bluetooth: L2CAP: validate MPS and MTU in ECRED connection response Joas Antonio dos Santos
2026-11-10  3:26 ` Joas Antonio dos Santos via B4 Relay
2026-11-10 11:19 ` [bluetooth-next,v2] " bluez.test.bot
2026-11-10 16:10 ` 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=179432701267.4062787.11305401861516612930.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=joasantonio108@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    /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.