Bluetooth: Fix triggering BR/EDR L2CAP Connect too early
authorJohan Hedberg <johan.hedberg@intel.com>
Fri, 11 Apr 2014 19:02:31 +0000 (12:02 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 7 Jun 2014 17:28:16 +0000 (10:28 -0700)
commit5e3ccae03cc3a26f535067c26e8f65d46679302f
tree561c9a70b784d2e1576733effadeaab047165aeb
parentf5ad14928afcc5c2b1c2722c7e935842ad512b0d
Bluetooth: Fix triggering BR/EDR L2CAP Connect too early

commit 9eb1fbfa0a737fd4d3a6d12d71c5ea9af622b887 upstream.

Commit 1c2e004183178 introduced an event handler for the encryption key
refresh complete event with the intent of fixing some LE/SMP cases.
However, this event is shared with BR/EDR and there we actually want to
act only on the auth_complete event (which comes after the key refresh).

If we do not do this we may trigger an L2CAP Connect Request too early
and cause the remote side to return a security block error.

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