Hi Mikhail, On Mon, May 23, 2016 at 12:57 PM, Mikhail Krivtsov <mikhail.krivtsov@xxxxxxxxx> wrote: > When bt_gatt_client receives 'indication' it sends 'confirmation'. > 'confirmation' sending was broken after adding support for 'clones' of > bt_gatt_client. In addition to first bt_gatt_client each clone also > sends 'confirmation'. > > # > ACL Data RX: Handle 69 flags 0x02 dlen 27 > # ATT: Handle Value Indication (0x1d) len 22 > # Handle: 0x001f > # Data: 68656c6c6f2027302e302e302e303a3532353332 > # < ACL Data TX: Handle 69 flags 0x00 dlen 5 > # ATT: Handle Value Confirmation (0x1e) len 0 > # < ACL Data TX: Handle 69 flags 0x00 dlen 5 > # ATT: Handle Value Confirmation (0x1e) len 0 > > Extra confirmation sent by clone confuses remote side. When bluetooth > daemon receives extra confirmation it breaks connection. > > Attached patch fixes the issue limiting confirmation sending to single > bt_gatt_client. I went ahead and applied this fix, thanks for the contribution. *Next time please do follow the instruction under HACKING and send as a proper patch. -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
