[PATCH BlueZ v2] l2test: Attempt to use BT_SNDMTU if output MTU has been set

[PATCH BlueZ v2] l2test: Attempt to use BT_SNDMTU if output MTU has been set

[Luiz Augusto von Dentz]

From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

With the suggested fixes for L2CAP/ECFC/BV-27-C the kernel shall be
able to accept setsockopt(BT_SNDMTU) in order for an applications
to require a minimal output MTU greater than 64.

Fixes: https://github.com/bluez/bluez/issues/1895
---
 tools/l2test.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/tools/l2test.c b/tools/l2test.c
index 7eecf1364492..2cf3a47e7cdf 100644
--- a/tools/l2test.c
+++ b/tools/l2test.c
@@ -318,6 +318,13 @@ static int setopts(int sk, struct l2cap_options *opts)
 		}
 	}
 
+	/* Older kernel versions may not support BT_SNDMTU so don't check its
+	 * return.
+	 */
+	if (opts->omtu)
+		setsockopt(sk, SOL_BLUETOOTH, BT_SNDMTU, &opts->omtu,
+				sizeof(opts->omtu));
+
 	return setsockopt(sk, SOL_BLUETOOTH, BT_RCVMTU, &opts->imtu,
 							sizeof(opts->imtu));
 }
-- 
2.52.0

RE: [BlueZ,v2] l2test: Attempt to use BT_SNDMTU if output MTU has been set

[bluez.test.bot]

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1056016

---Test result---

Test Summary:
CheckPatch                    PENDING   0.47 seconds
GitLint                       PENDING   0.44 seconds
BuildEll                      PASS      19.80 seconds
BluezMake                     PASS      645.32 seconds
MakeCheck                     PASS      18.68 seconds
MakeDistcheck                 PASS      239.82 seconds
CheckValgrind                 PASS      290.83 seconds
CheckSmatch                   PASS      346.84 seconds
bluezmakeextell               PASS      180.94 seconds
IncrementalBuild              PENDING   0.36 seconds
ScanBuild                     PASS      1000.33 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth

Re: [PATCH BlueZ v2] l2test: Attempt to use BT_SNDMTU if output MTU has been set

[patchwork-bot+bluetooth]

Hello:

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

On Fri, 20 Feb 2026 15:08:50 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> With the suggested fixes for L2CAP/ECFC/BV-27-C the kernel shall be
> able to accept setsockopt(BT_SNDMTU) in order for an applications
> to require a minimal output MTU greater than 64.
> 
> Fixes: https://github.com/bluez/bluez/issues/1895
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2] l2test: Attempt to use BT_SNDMTU if output MTU has been set
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=290f9973c906

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