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)
committerJohan Hedberg <johan.hedberg@intel.com>
Fri, 25 Apr 2014 06:47:15 +0000 (09:47 +0300)
commit9eb1fbfa0a737fd4d3a6d12d71c5ea9af622b887
treed57f0f40f004ee2ba15575ce579161b46025c826
parent3c49aa852e00978ba2f1a4d1e4598a0c669a5347
Bluetooth: Fix triggering BR/EDR L2CAP Connect too early

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>
Cc: stable@vger.kernel.org
net/bluetooth/hci_event.c