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)
committerJiri Slaby <jslaby@suse.cz>
Fri, 6 Jun 2014 10:38:23 +0000 (12:38 +0200)
commit933d4bfa946ca681b33ff29b4994887c5787968a
treeb49e3fe313340ce4155f6f96560441d542eb3ded
parentfde051cada91a1ae03eec8b8dd13b09379cf9dbf
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: Jiri Slaby <jslaby@suse.cz>
net/bluetooth/hci_event.c