All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH 1/2] android/gatt: Fix initial setting of MTU
@ 2015-01-29 19:54 Lukasz Rymanowski
  2015-01-29 19:54 ` [PATCH 2/2] android/gatt: Remove not used variable Lukasz Rymanowski
  0 siblings, 1 reply; 2+ messages in thread
From: Lukasz Rymanowski @ 2015-01-29 19:54 UTC (permalink / raw)
  To: linux-bluetooth; +Cc: Lukasz Rymanowski

Initial setting of MTU should be IMTU. This is actually our assumption
in other part of code, that IMTU is something we start with and change
if needed after exchange MTU procedure.

If we are not able to get IMTU from the socket just disconnect, there is
something wrong going on.

Without this patch you can face the issue with following scenario:
1. On connection complete MTU is set to 23
2. BfA sends Exchange MTU Request with MTU set to IMTU
3. Remote device response with MTU equal to what BfA sends
4. In that case, since remote MTU is equal to ours, there is no
update in bt_att, so bt_att keep using  MTU = 23
5. Remote sends packets highier then 23 and bt_att start to drop not
complete packets.

Issue found and fix tested on UPF50
---
 android/gatt.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/android/gatt.c b/android/gatt.c
index 466c1ea..ddec9ad 100644
--- a/android/gatt.c
+++ b/android/gatt.c
@@ -1511,8 +1511,12 @@ static void connect_cb(GIOChannel *io, GError *gerr, gpointer user_data)
 	}
 
 	if (!bt_io_get(io, &gerr, BT_IO_OPT_IMTU, &mtu, BT_IO_OPT_CID, &cid,
-				BT_IO_OPT_INVALID) || cid == ATT_CID)
-		mtu = ATT_DEFAULT_LE_MTU;
+							BT_IO_OPT_INVALID)) {
+		error("gatt: Could not get imtu: %s", gerr->message);
+		device_set_state(dev, DEVICE_DISCONNECTED);
+		status = GATT_FAILURE;
+		goto reply;
+	}
 
 	attrib = g_attrib_new(io, mtu);
 	if (!attrib) {
-- 
1.8.4


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* [PATCH 2/2] android/gatt: Remove not used variable
  2015-01-29 19:54 [PATCH 1/2] android/gatt: Fix initial setting of MTU Lukasz Rymanowski
@ 2015-01-29 19:54 ` Lukasz Rymanowski
  0 siblings, 0 replies; 2+ messages in thread
From: Lukasz Rymanowski @ 2015-01-29 19:54 UTC (permalink / raw)
  To: linux-bluetooth; +Cc: Lukasz Rymanowski

---
 android/gatt.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/android/gatt.c b/android/gatt.c
index ddec9ad..8242996 100644
--- a/android/gatt.c
+++ b/android/gatt.c
@@ -1490,7 +1490,6 @@ static void connect_cb(GIOChannel *io, GError *gerr, gpointer user_data)
 	uint32_t status;
 	GAttrib *attrib;
 	uint16_t mtu;
-	uint16_t cid;
 
 	if (dev->state != DEVICE_CONNECT_READY) {
 		error("gatt: Device not in a connecting state!?");
@@ -1510,8 +1509,7 @@ static void connect_cb(GIOChannel *io, GError *gerr, gpointer user_data)
 		goto reply;
 	}
 
-	if (!bt_io_get(io, &gerr, BT_IO_OPT_IMTU, &mtu, BT_IO_OPT_CID, &cid,
-							BT_IO_OPT_INVALID)) {
+	if (!bt_io_get(io, &gerr, BT_IO_OPT_IMTU, &mtu, BT_IO_OPT_INVALID)) {
 		error("gatt: Could not get imtu: %s", gerr->message);
 		device_set_state(dev, DEVICE_DISCONNECTED);
 		status = GATT_FAILURE;
-- 
1.8.4


^ permalink raw reply related	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-01-29 19:54 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-01-29 19:54 [PATCH 1/2] android/gatt: Fix initial setting of MTU Lukasz Rymanowski
2015-01-29 19:54 ` [PATCH 2/2] android/gatt: Remove not used variable Lukasz Rymanowski

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.