Bluetooth: Use connection address for reporting connection failures
authorMarcel Holtmann <marcel@holtmann.org>
Tue, 18 Feb 2014 22:22:20 +0000 (14:22 -0800)
committerJohan Hedberg <johan.hedberg@intel.com>
Wed, 19 Feb 2014 04:08:47 +0000 (06:08 +0200)
When reporting connect failed events to userspace, use the address
of the connection and not the address from the HCI event.

This change is strictly speaking not needed since BR/EDR does not
have the concept of resolvable random addresses. It is more for
making the code consistent.

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

index d7c709519e31fd7c01fac0176de284f90fd4cbcc..22bfc5c17e7f792c7735d43a937c2eaa9aa3e44d 100644 (file)
@@ -1704,7 +1704,7 @@ static void hci_conn_complete_evt(struct hci_dev *hdev, struct sk_buff *skb)
        } else {
                conn->state = BT_CLOSED;
                if (conn->type == ACL_LINK)
-                       mgmt_connect_failed(hdev, &ev->bdaddr, conn->type,
+                       mgmt_connect_failed(hdev, &conn->dst, conn->type,
                                            conn->dst_type, ev->status);
        }