Bluetooth: Don't treat connection timeout as a failure
authorJohan Hedberg <johan.hedberg@intel.com>
Thu, 3 Dec 2015 10:45:20 +0000 (12:45 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Wed, 9 Dec 2015 23:51:51 +0000 (00:51 +0100)
commitacb9f911ea1f828822001d72b21f7cc06e6718c7
tree18c72264c8452cac3fc6b04cbc00a77aad3d149d
parent2f99536a5b34d5b0f54723067d68f6cef3f0fdc6
Bluetooth: Don't treat connection timeout as a failure

When we're doing background scanning and connection attempts it's
possible we timeout trying to connect and go back to scanning again.
The timeout triggers a HCI_LE_Create_Connection_Cancel which will
trigger a Connection Complete with "Unknown Connection Identifier"
error status. Since we go back to scanning this isn't really a failure
and shouldn't be presented as such to user space through mgmt.

The exception to this is if the connection attempt was due to an
explicit request on an L2CAP socket (indicated by
params->explicit_connect being true). Since the socket will get an
error it's consistent to also notify the failure on mgmt in this case.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
net/bluetooth/hci_conn.c