Skip to contentSkip to conversation

bluez5: set L2CAP IMTU for OBEX profile listeners

PATCH Superseded Wei Deng 2 participants 5 messages Jun 5 – Jun 26

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore

Wei Deng

author
#0 lore raw

PATCH 1/1 bluez5: set L2CAP IMTU for OBEX profile listeners

Backport upstream fix that adds an imtu field to default_settings for OBEX profiles (OPP, FTP, PBAP, MAS, MNS) and applies it to the L2CAP listening socket via bt_io_set(). Without this, the listening socket advertises the L2CAP minimum of 672 bytes in L2CAP_CONFIGURATION_RSP, limiting the peer's outgoing PDU size and degrading Rx throughput.

Upstream-Status: Backport [bluez/bluez@646014a]

---
 meta/recipes-connectivity/bluez5/bluez5.inc   |   1 +
 ...2CAP-IMTU-for-OBEX-profile-listeners.patch | 118 ++++++++++++++++++
 2 files changed, 119 insertions(+)
 create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-profile-Set-L2CAP-IMTU-for-OBEX-profile-listeners.patch
meta/recipes-connectivity/bluez5/bluez5.inc +1 -0
index e827d0a6d7..71bceddb21 100644
@@ -72,6 +72,7 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/bluetooth/bluez-${PV}.tar.xz \
            file://0001-tools-Work-around-broken-stdin-handling-in-home-made.patch \
            file://0001-gatt-client-Fix-use-after-free-caused-by-reentrant-c.patch \
            file://0001-transport-Fix-set-volume-failure-with-invalid-device.patch \
+           file://0001-profile-Set-L2CAP-IMTU-for-OBEX-profile-listeners.patch \
            "
 S = "${UNPACKDIR}/bluez-${PV}"
 
meta/recipes-connectivity/bluez5/bluez5/0001-profile-Set-L2CAP-IMTU-for-OBEX-profile-listeners.patch new file +118 -0

118 lines not on this page · raw message

Signature · 1 line
2.34.1
author
#1 lore raw

Hi Yoann,

This patch was merged to OE-core master on 2026-06-11 (commit 13cb97f). Could you please cherry-pick it to the wrynose branch as well? It fixes an OBEX Rx throughput regression caused by an incorrect L2CAP IMTU being advertised on listening sockets.

Thanks,

Quoted 9 lines · Wei Deng

Backport upstream fix that adds an imtu field to default_settings for OBEX profiles (OPP, FTP, PBAP, MAS, MNS) and applies it to the L2CAP listening socket via bt_io_set(). Without this, the listening socket advertises the L2CAP minimum of 672 bytes in L2CAP_CONFIGURATION_RSP, limiting the peer's outgoing PDU size and degrading Rx throughput.

Upstream-Status: Backport [bluez/bluez@646014a]

---

--
Best Regards,
Wei Deng

#2 lore raw
Quoted 7 lines · Wei Deng

Hi Yoann,

This patch was merged to OE-core master on 2026-06-11 (commit 13cb97f). Could you please cherry-pick it to the wrynose branch as well? It fixes an OBEX Rx throughput regression caused by an incorrect L2CAP IMTU being advertised on listening sockets.

Hello,

I've noted to consider it. Looks good at a quick glance. Ping back if you don't see it in the next wrynose review series.

Regards,

Quoted 19 lines

Thanks,

Quoted 9 lines · Wei Deng

Backport upstream fix that adds an imtu field to default_settings for OBEX profiles (OPP, FTP, PBAP, MAS, MNS) and applies it to the L2CAP listening socket via bt_io_set(). Without this, the listening socket advertises the L2CAP minimum of 672 bytes in L2CAP_CONFIGURATION_RSP, limiting the peer's outgoing PDU size and degrading Rx throughput.

Upstream-Status: Backport [bluez/bluez@646014a]

---

--
Best Regards,
Wei Deng

Signature · 2 lines
Yoann Congal
Smile ECS
#3 lore raw
Quoted 13 lines · Yoann Congal

Le jeu. 25 juin 2026 à 05:47, Wei Deng <[email protected]> a écrit :

Quoted 7 lines

Hi Yoann,

This patch was merged to OE-core master on 2026-06-11 (commit 13cb97f). Could you please cherry-pick it to the wrynose branch as well? It fixes an OBEX Rx throughput regression caused by an incorrect L2CAP IMTU being advertised on listening sockets.

Quoted 5 lines

Hello,

I've noted to consider it. Looks good at a quick glance. Ping back if you don't see it in the next wrynose review series.

... except it does not apply cleanly on wrynose. Can you send a backported patch?

Thanks!

Quoted 29 lines

Regards,

Quoted 11 lines

Thanks,

Quoted 6 lines · Wei Deng

Backport upstream fix that adds an imtu field to default_settings for OBEX profiles (OPP, FTP, PBAP, MAS, MNS) and applies it to the L2CAP listening socket via bt_io_set(). Without this, the listening socket advertises the L2CAP minimum of 672 bytes in L2CAP_CONFIGURATION_RSP, limiting the peer's outgoing PDU size and degrading Rx throughput.

Quoted 8 lines
Quoted 3 lines

Upstream-Status: Backport [bluez/bluez@646014a]

---

--
Best Regards,
Wei Deng

--
Yoann Congal
Smile ECS

Signature · 2 lines
Yoann Congal
Smile ECS
author
#4 lore raw

Hi Yoann,

Quoted 17 lines · Yoann Congal

Le jeu. 25 juin 2026 à 12:42, Yoann Congal <[email protected]> a écrit :

Le jeu. 25 juin 2026 à 05:47, Wei Deng <[email protected]> a écrit :

Quoted 7 lines

Hi Yoann,

This patch was merged to OE-core master on 2026-06-11 (commit 13cb97f). Could you please cherry-pick it to the wrynose branch as well? It fixes an OBEX Rx throughput regression caused by an incorrect L2CAP IMTU being advertised on listening sockets.

Hello,

Quoted 7 lines

I've noted to consider it. Looks good at a quick glance. Ping back if you don't see it in the next wrynose review series.

... except it does not apply cleanly on wrynose. Can you send a backported patch?

Thanks!

The reason the original patch does not apply cleanly on wrynose is that OE-core master has three additional bluez5 patches that are not yet in wrynose:

- bluez5: fix set volume failure (master ec27d1e5cf5, Jinwang Li, 2026-05-29)
- bluez5: Fix sending extra bytes with MGMT_OP_ADD_EXT_ADV_DATA

    (master f143e23e2e3, Xiuzhuo Shang, 2026-06-05)

- bluez5: fix gatt cache sync issue (master 137eeffd4fa, Mengshi Wu, 2026-06-08)

These patches shift the SRC_URI context in bluez5.inc, causing the cherry-pick to fail.

I am sending a backport patch series of 4 patches to wrynose together. Please add to wrynose review series.

Thanks,

Signature · 2 lines
Best Regards,
Wei Deng