* [PATCH BlueZ v1] l2test: Attempt to use BT_SNDMTU if output MTU has been set
@ 2026-02-20 17:40 Luiz Augusto von Dentz
2026-02-20 18:50 ` [BlueZ,v1] " bluez.test.bot
0 siblings, 1 reply; 2+ messages in thread
From: Luiz Augusto von Dentz @ 2026-02-20 17:40 UTC (permalink / raw)
To: linux-bluetooth
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 | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/tools/l2test.c b/tools/l2test.c
index 7eecf1364492..b085c8d05453 100644
--- a/tools/l2test.c
+++ b/tools/l2test.c
@@ -318,6 +318,12 @@ static int setopts(int sk, struct l2cap_options *opts)
}
}
+ /* Older kernel versions may not support BT_SNDMTU so don't check its
+ * return.
+ */
+ 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
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-02-20 18:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-20 17:40 [PATCH BlueZ v1] l2test: Attempt to use BT_SNDMTU if output MTU has been set Luiz Augusto von Dentz
2026-02-20 18:50 ` [BlueZ,v1] " bluez.test.bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox