summaryrefslogtreecommitdiffstats
path: root/net/bluetooth
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2009-01-15 21:57:03 +0100
committerMarcel Holtmann <marcel@holtmann.org>2009-02-27 06:14:25 +0100
commitc89b6e6bda4c8021195778f47567d0cc9dbfe7ec (patch)
treebabe74bb0f318f26c572859e067a4c8d1d4d43a9 /net/bluetooth
parent71aeeaa1fd88fe7446391e0553336f0e0c2cfe6a (diff)
downloadlinux-stable-c89b6e6bda4c8021195778f47567d0cc9dbfe7ec.tar.gz
linux-stable-c89b6e6bda4c8021195778f47567d0cc9dbfe7ec.tar.bz2
linux-stable-c89b6e6bda4c8021195778f47567d0cc9dbfe7ec.zip
Bluetooth: Fix SCO state handling for incoming connections
When the remote device supports only SCO connections, on receipt of the HCI_EV_CONN_COMPLETE event packet, the connect state is changed to BT_CONNECTED, but the socket state is not updated. Hence, the connect() call times out even though the SCO connection has been successfully established. Based on a report by Jaikumar Ganesh <jaikumar@google.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth')
-rw-r--r--net/bluetooth/hci_event.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
index f91ba690f5d2..beea9dbb6562 100644
--- a/net/bluetooth/hci_event.c
+++ b/net/bluetooth/hci_event.c
@@ -914,7 +914,8 @@ static inline void hci_conn_complete_evt(struct hci_dev *hdev, struct sk_buff *s
if (ev->status) {
hci_proto_connect_cfm(conn, ev->status);
hci_conn_del(conn);
- }
+ } else if (ev->link_type != ACL_LINK)
+ hci_proto_connect_cfm(conn, ev->status);
unlock:
hci_dev_unlock(hdev);