Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Michael Bommarito <michael.bommarito@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v4] Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig
Date: Fri, 29 May 2026 15:50:06 +0000	[thread overview]
Message-ID: <178006980639.1863338.949491085848343135.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260521144518.1361335-1-michael.bommarito@gmail.com>

Hello:

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

On Thu, 21 May 2026 10:45:17 -0400 you wrote:
> net/bluetooth/l2cap_core.c:l2cap_sig_channel() accepts BR/EDR
> signaling packets up to the channel MTU and dispatches each command
> without enforcing the signaling MTU (MTUsig). A Bluetooth BR/EDR peer
> within radio range can send a fixed-channel CID 0x0001 packet that is
> larger than MTUsig and contains many L2CAP_ECHO_REQ commands before
> pairing. In a real-radio stock-kernel run, one 681-byte signaling
> packet containing 168 zero-length ECHO_REQ commands made the target
> transmit 168 ECHO_RSP frames over about 220 ms.
> 
> [...]

Here is the summary with links:
  - [v4] Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig
    https://git.kernel.org/bluetooth/bluetooth-next/c/a6273f046450

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-05-29 15:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 13:50 [PATCH v2] Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig Michael Bommarito
2026-05-20 14:00 ` Luiz Augusto von Dentz
2026-05-20 14:12   ` Michael Bommarito
2026-05-20 15:18     ` Luiz Augusto von Dentz
2026-05-20 15:23       ` Michael Bommarito
2026-05-20 16:15         ` Luiz Augusto von Dentz
2026-05-20 14:48 ` [v2] " bluez.test.bot
2026-05-21  0:05 ` [PATCH v3] " Michael Bommarito
2026-05-21 12:51   ` Luiz Augusto von Dentz
2026-05-21 14:45   ` [PATCH v4] " Michael Bommarito
2026-05-21 17:23     ` [v4] " bluez.test.bot
2026-05-21 19:08     ` bluez.test.bot
2026-05-29 15: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=178006980639.1863338.949491085848343135.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=michael.bommarito@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