archives/linux
1
0
Fork 0
mirror of https://github.com/torvalds/linux.git synced 2026-03-14 00:56:20 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Bluetooth: L2CAP: Fix attempting to adjust outgoing MTU

Browse source 
Configuration request only configure the incoming direction of the peer
initiating the request, so using the MTU is the other direction shall
not be used, that said the spec allows the peer responding to adjust:

Bluetooth Core 6.1, Vol 3, Part A, Section 4.5

 'Each configuration parameter value (if any is present) in an
 L2CAP_CONFIGURATION_RSP packet reflects an ‘adjustment’ to a
 configuration parameter value that has been sent (or, in case of
 default values, implied) in the corresponding
 L2CAP_CONFIGURATION_REQ packet.'

That said adjusting the MTU in the response shall be limited to ERTM
channels only as for older modes the remote stack may not be able to
detect the adjustment causing it to silently drop packets.

Link: https://github.com/bluez/bluez/issues/1422
Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/149
Link: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4793
Fixes: 042bb9603c ("Bluetooth: L2CAP: Fix L2CAP MTU negotiation")
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
This commit is contained in:
Luiz Augusto von Dentz 2025-07-16 09:40:49 -04:00
parent 4301595579
commit d24e4a7fed
1 changed files with 21 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

26
net/bluetooth/l2cap_core.c
View file

@ -3520,12 +3520,28 @@ done:
/* Configure output options and let the other side know
* which ones we don't like. */
/* If MTU is not provided in configure request, use the most recently
* explicitly or implicitly accepted value for the other direction,
* or the default value.
/* If MTU is not provided in configure request, try adjusting it
* to the current output MTU if it has been set
*
* Bluetooth Core 6.1, Vol 3, Part A, Section 4.5
*
* Each configuration parameter value (if any is present) in an
* L2CAP_CONFIGURATION_RSP packet reflects an ‘adjustment’ to a
* configuration parameter value that has been sent (or, in case
* of default values, implied) in the corresponding
* L2CAP_CONFIGURATION_REQ packet.
*/
if (mtu == 0)
mtu = chan->imtu ? chan->imtu : L2CAP_DEFAULT_MTU;
if (!mtu) {
/* Only adjust for ERTM channels as for older modes the
* remote stack may not be able to detect that the
* adjustment causing it to silently drop packets.
*/
if (chan->mode == L2CAP_MODE_ERTM &&
chan->omtu && chan->omtu != L2CAP_DEFAULT_MTU)
mtu = chan->omtu;
else
mtu = L2CAP_DEFAULT_MTU;
}
if (mtu < L2CAP_DEFAULT_MIN_MTU)
result = L2CAP_CONF_UNACCEPT;